[
https://jira.jboss.org/browse/JBRULES-2559?page=com.atlassian.jira.plugin...
]
Chris DeLashmutt updated JBRULES-2559:
--------------------------------------
Comment: was deleted
(was: I added what I think is a proper clone implementation to MVELDataProvider, but now
the problem I'm seeing is that when MVELDataProvider is serialized, it doesn't
save the prototype and requiredDeclarations properties. It seems like those properties
get re-set properly via AbstractRuleBase's readExternal method when it calls
Package.getDialectRuntimeRegistry.onBeforeExecute() on all the packages. However,
ReteooBuilder seems to get it's own clones of the MVELDataProvider and it has no such
call to onBeforeExecute in it's readExternal method. I'll see if I can implement
something.)
Problem with Collect statement from a source that is a previous
declaration after an OR'd group in MVEL dialect
---------------------------------------------------------------------------------------------------------------
Key: JBRULES-2559
URL:
https://jira.jboss.org/browse/JBRULES-2559
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-core
Affects Versions: 5.1.0.M2
Reporter: Chris DeLashmutt
Assignee: Mark Proctor
Attachments: patch.txt
When using a Collect statement that is sourced from a nested property of a bound pattern
and it follows an OR'd group of evals, the bound pattern seems to be pointing to the
wrong object in the tuple. I have attached a diff for drools-compiler that includes a new
test case in FirstOrderLogicTest and DRL that exhibits this problem.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira