[
https://issues.jboss.org/browse/JBRULES-3690?page=com.atlassian.jira.plug...
]
Esteban Aliverti updated JBRULES-3690:
--------------------------------------
Attachment: RuleNotBeingFired.zip
Attaching test project. The test contains 2 rules. The execution of the first rule should
activate the second one. This is not happening.
If, in DataSample.java, you change the methods isEmpty() and setEmpty() to something else,
i.e. isXempty() and setXempty() and change the @Modify in addValue() to
@Modify({"values","xempty"}) the test works as expected.
Property Reactive: bitmask not being correctly calculated when field
name is 'empty'
------------------------------------------------------------------------------------
Key: JBRULES-3690
URL:
https://issues.jboss.org/browse/JBRULES-3690
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-compiler
Affects Versions: 5.5.0.Final
Reporter: Esteban Aliverti
Assignee: Mario Fusco
Labels: property_reactive
Attachments: RuleNotBeingFired.zip
When using Property Reactive facts, the property name 'empty' prevents rules to
be activated.
If the property name is changed, rules work as expected.
The problem could be related to the fact that 'empty' is internally translated to
'isEmpty()' and this could cause problems when the pattern's bitmask is
calculated.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira