[
https://issues.jboss.org/browse/DROOLS-570?page=com.atlassian.jira.plugin...
]
Davide Sottara commented on DROOLS-570:
---------------------------------------
Confirmed..
the problem happens during the generation of the second rule's consequence.
See org.drools.core.rule.builder.dialect.asm.ConsequenceGenerator#235: the method
"getQueueIndex" has actually been renamed "getIndex".
Unfortunately 6.1 has just been released, so you will have to use a SNAPSHOT or apply the
fix yourself and recompile the code.
A workaround, use mvel rather than java in the second rule adding the attribute:
{code}
dialect "mvel"
{code}
Thanks for reporting this
Davide
Rule inheritance fails when using or pattern binding
----------------------------------------------------
Key: DROOLS-570
URL:
https://issues.jboss.org/browse/DROOLS-570
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 6.0.1.Final
Environment: Windows 7 VM. Running drools using a JUnit driver
Reporter: Eugene Shvartsman
Assignee: Mark Proctor
Attachments: tester-module.7z
I've found a certain combination of rules (when using inheritance) that causes drools
to throw the following exception:
http://pastebin.com/xxq5ZtAC
The rules that cause this exception to occur can be found here:
http://pastebin.com/wM6rWY8L
I've simplified my original rules down to the lowest level of detail that still
throws the exception. The exception is no longer thrown if I:
1. Don't use rule inheritance
2. Don't have an or statement
3. Don't reference an LHS defined variable in the RHS of ruleB
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)