Bug 814029 - 'or' CE does not work with enabled, salience or timer expressions
Summary: 'or' CE does not work with enabled, salience or timer expressions
Keywords:
Status: VERIFIED
Alias: None
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: BRE (Expert, Fusion)
Version: BRMS 5.3.0.GA
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ER6
: BRMS 5.3.0.GA
Assignee: Nobody
QA Contact: Lukáš Petrovický
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-19 04:07 UTC by Mark Proctor
Modified: 2021-04-09 12:48 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
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 JBRULES-3469 0 None Closed 'or' CE does not work with enabled, salience or timer expressions 2012-05-18 10:22:07 UTC

Description Mark Proctor 2012-04-19 04:07:26 UTC 
If 'or' CE is used iwth salience or enabled exceptions this would give a runtime stack trace error.

This is fixed in mater has now been backported to 5.3.x. Master included an additional feature of timer expressions, which was part of the fix on mater. I have removed this from the backport.
master:
https://source.jboss.org/changelog/Drools?cs=e8728aacefac4276284158b58a7564d5de1f6b83

5.3.x:
https://source.jboss.org/changelog/Drools?cs=336bce61e4b274f7dc08bbe2dd843885bdde8028
Comment 1 Lukáš Petrovický 2012-04-19 05:51:47 UTC 
I see this is already merged - moving this to MODIFIED for QE to look at it.
Comment 2 Mark Proctor 2012-04-19 17:59:31 UTC 
"I see this is already merged - moving this to MODIFIED for QE to look at it."

Yes already merged, was just waiting for the build to show blue before changing status.

Also added the JIRA link.
Comment 3 Ryan Zhang 2012-04-23 07:38:54 UTC 
Update status to ON_QA. Please verify them against ER6.
Comment 5 Lukáš Petrovický 2012-05-17 13:42:29 UTC 
This has both been reported and committed by Mark. VERIFIED
Note You need to log in before you can comment on or make changes to this bug.