[
http://jira.jboss.com/jira/browse/JBRULES-667?page=comments#action_12352850 ]
Frederic Burlet commented on JBRULES-667:
-----------------------------------------
A workaround is to add an identifier for the fact. The rule described in the ticket then
becomes;
.... when
MyBean(property == value_1) or MyBean(property == value_2)
$ob : OtherBean( )
then....
...and no NPE anymore :o)
Combination of Or condition and simple fact fails to evaluate
-------------------------------------------------------------
Key: JBRULES-667
URL:
http://jira.jboss.com/jira/browse/JBRULES-667
Project: JBoss Rules
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 3.1-m1
Environment: Debian Linux Unstable
Java 1.4
Reporter: Frederic Burlet
Assigned To: Mark Proctor
Attachments: conditions-test.tar.gz
When we have a lhs containing a combination of or condition and simple fact like:
.... when
MyBean(property == value_1) or MyBean(property == value_2)
OtherBean( )
then....
The engine throwing a NPE when adding rules.
It also fails with the same error when conditions are written in a different order.
See attached test case in order to reproduce. This has been tested against the trunk
revision #9453.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira