[
http://jira.jboss.com/jira/browse/JBRULES-749?page=all ]
Edson Tirelli closed JBRULES-749.
---------------------------------
Fix Version/s: 3.1-m2
Resolution: Out of Date
I just tested in trunk and it is not raising exceptions anymore. The only problem I found
is that as no-loop only prevents the same rule from activating, the attached rule-set is
in loop because of rules 2 and 4. A simple fix, just for the sake of the test is to
rewrite rule 2 as:
rule "Rule-2"
no-loop true
when
$m : Machine( entryAlreadyCreated == false )
then
System.out.println("DEBUG [Rule-2]---> Add Machine to MachineEntry");
MachineEntry me = new MachineEntry();
me.setMachine($m);
assert(me);
$m.setEntryAlreadyCreated( true );
modify( $m );
end
Thank you for reporting and providing test cases. Let us know if you are still having
problems.
Null Pointer Exception
in"org.drools.reteoo.RuleTerminalNode.retractTuple"
--------------------------------------------------------------------------
Key: JBRULES-749
URL:
http://jira.jboss.com/jira/browse/JBRULES-749
Project: JBoss Rules
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 3.1-m1
Environment: Windows XP SP2, JVM1.4
Reporter: Michael Anstis
Assigned To: Edson Tirelli
Fix For: 3.1-m2
Attachments: jira-749.jar, Re rules-users Null Pointer
Exceptioninorg.drools.reteoo.RuleTerminalNode.retractTuple.txt
Null Pointer Exception thrown when running rule "Rule-4 (Null Pointer
Exception)" see attachment for complete, re-producible example.
--
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