Bug 780620 (SOA-3058)

Summary: Rules do not fire according to salience after multiple fact updates
Product: [JBoss] JBoss Enterprise SOA Platform 5 Reporter: Matt Davis <mattd>
Component: JBoss RulesAssignee: Tihomir Surdilovic <tsurdilo>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 5.1.0 GACC: tsurdilo
Target Milestone: ---   
Target Release: 5.1.0 GA   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-3058
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-05-14 03:12:28 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

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