Bug 780620 (SOA-3058) - Rules do not fire according to salience after multiple fact updates
Summary: Rules do not fire according to salience after multiple fact updates
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-3058
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: JBoss Rules
Version: 5.1.0 GA
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 5.1.0 GA
Assignee: Tihomir Surdilovic
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-05 12:56 UTC by Matt Davis
Modified: 2011-10-04 15:01 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-14 03:12:28 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-3058 0 None None None Never

Description Matt Davis 2011-05-05 12:56:55 UTC 
Help Desk Ticket Reference: https://c.na7.visual.force.com/apex/Case_View?id=500A0000007AQwS&sfdc.override=1
project_key: SOA

Need fix for BRMS-586 included in the JBoss SOA Platform.
Comment 1 Matt Davis 2011-05-05 12:57:42 UTC 
Link: Added: This issue Cloned from JBRULES-2942
Comment 2 Matt Davis 2011-05-05 12:57:42 UTC 
Link: Added: This issue Cloned from BRMS-586
Comment 3 Tihomir Surdilovic 2011-05-14 03:11:26 UTC 
Resolved as part of BRMS-586 fix check-in into the BRMS 5.1.x branch
Comment 4 Tihomir Surdilovic 2011-05-14 03:12:28 UTC 
Release Notes Text: Added: Fix is in the 5.1. branch of BRMS. If next SOA version uses BRMS 5.2 this fix will also be available there as well.
Comment 5 RH Bugzilla Integration 2011-09-02 00:04:20 UTC 
Bugzilla References: Added: https://bugzilla.redhat.com/show_bug.cgi?id=724724
Comment 6 trev 2011-10-04 15:01:07 UTC 
Bugzilla References: Removed: https://bugzilla.redhat.com/show_bug.cgi?id=724724 Added: https://bugzilla.redhat.com/show_bug.cgi?id=724724
Note You need to log in before you can comment on or make changes to this bug.