[
https://issues.jboss.org/browse/JBRULES-3691?page=com.atlassian.jira.plug...
]
Esteban Aliverti updated JBRULES-3691:
--------------------------------------
Attachment: RuleNotBeingFired.zip
The test contained in this project fails.
The test contains 2 rules, one of them having:
modify($d){
addValue($re.getParameter(), $re.getValue())
}
This should create an activation of the second rule, but it doesn't.
If instead of that modify, you do:
modify($d){
addValue($p, $v)
}
The second rule is activated as expected. Please note that the 2 modifies have the same
meaning and should behave the same.
Property Reactive: using nested accessor in modify() seems to prevent
the correct re-evaluation of the rules.
--------------------------------------------------------------------------------------------------------------
Key: JBRULES-3691
URL:
https://issues.jboss.org/browse/JBRULES-3691
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-compiler, drools-core
Affects Versions: 6.0.0.Alpha1
Reporter: Esteban Aliverti
Assignee: Mario Fusco
Labels: property_reactive
Attachments: RuleNotBeingFired.zip
The usage of nested accessors in modify() seems to prevent rules to be re-evaluated, or
the re-evaluation result is not the expected one.
--
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