[
http://jira.jboss.com/jira/browse/JBRULES-612?page=all ]
Edson Tirelli resolved JBRULES-612.
-----------------------------------
Fix Version/s: 3.1-m1
Resolution: Done
Problem fixed in both trunk and 3.0.x branch, as detailed bellow.
Thank you for reporting and providing test cases. This was a great find as it showed up
only on a very specific scenario.
Let me know if you have any other problem.
$ svn log -r 8999 -v ../jbrules-3.0.x/
------------------------------------------------------------------------
r8999 | tirelli | 2007-01-23 20:58:46 -0300 (Tue, 23 Jan 2007) | 8 lines
Changed paths:
A /labs/jbossrules/branches/3.0.x/drools-compiler/src/test/java/org/drools/FactA.java
A /labs/jbossrules/branches/3.0.x/drools-compiler/src/test/java/org/drools/FactB.java
A /labs/jbossrules/branches/3.0.x/drools-compiler/src/test/java/org/drools/FactC.java
M
/labs/jbossrules/branches/3.0.x/drools-compiler/src/test/java/org/drools/integrationtests/IntegrationCases.java
A
/labs/jbossrules/branches/3.0.x/drools-compiler/src/test/resources/org/drools/integrationtests/test_DynamicRules.drl
A
/labs/jbossrules/branches/3.0.x/drools-compiler/src/test/resources/org/drools/integrationtests/test_DynamicRules2.drl
M
/labs/jbossrules/branches/3.0.x/drools-core/src/main/java/org/drools/reteoo/Rete.java
M
/labs/jbossrules/branches/3.0.x/drools-core/src/main/java/org/drools/reteoo/ReteooBuilder.java
JBRULES-612:
* Fixed problem with identity removal constraint
* Reseting object type cache when a new node type is added to the network
* Fixing problem when updating more than one working memories attached to the same
rulebase
* Integration tests added
==================================================
$ svn log -r 9000 -v
------------------------------------------------------------------------
r9000 | tirelli | 2007-01-23 21:16:10 -0300 (Tue, 23 Jan 2007) | 8 lines
Changed paths:
A /labs/jbossrules/trunk/drools-compiler/src/test/java/org/drools/FactA.java (from
/labs/jbossrules/branches/3.0.x/drools-compiler/src/test/java/org/drools/FactA.java:8999)
A /labs/jbossrules/trunk/drools-compiler/src/test/java/org/drools/FactB.java (from
/labs/jbossrules/branches/3.0.x/drools-compiler/src/test/java/org/drools/FactB.java:8999)
A /labs/jbossrules/trunk/drools-compiler/src/test/java/org/drools/FactC.java (from
/labs/jbossrules/branches/3.0.x/drools-compiler/src/test/java/org/drools/FactC.java:8999)
M
/labs/jbossrules/trunk/drools-compiler/src/test/java/org/drools/integrationtests/IntegrationCases.java
A
/labs/jbossrules/trunk/drools-compiler/src/test/resources/org/drools/integrationtests/test_DynamicRules.drl
(from
/labs/jbossrules/branches/3.0.x/drools-compiler/src/test/resources/org/drools/integrationtests/test_DynamicRules.drl:8999)
A
/labs/jbossrules/trunk/drools-compiler/src/test/resources/org/drools/integrationtests/test_DynamicRules2.drl
(from
/labs/jbossrules/branches/3.0.x/drools-compiler/src/test/resources/org/drools/integrationtests/test_DynamicRules2.drl:8999)
M /labs/jbossrules/trunk/drools-core/src/main/java/org/drools/reteoo/Rete.java
M
/labs/jbossrules/trunk/drools-core/src/main/java/org/drools/reteoo/ReteooBuilder.java
M
/labs/jbossrules/trunk/drools-core/src/main/java/org/drools/reteoo/builder/ColumnBuilder.java
JBRULES-612:
* Fixed problem with identity removal constraint
* Reseting object type cache when a new node type is added to the network
* Fixing problem when updating more than one working memories attached to the same
rulebase
* Integration tests added
NPE on asserting facts before reading rules with retract
--------------------------------------------------------
Key: JBRULES-612
URL:
http://jira.jboss.com/jira/browse/JBRULES-612
Project: JBoss Rules
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 3.0.5
Environment: Windows XP, JDK 1.5.0_07
Reporter: Justine Hlista
Assigned To: Edson Tirelli
Fix For: 3.0.6, 3.1-m1
Attachments: test.tar.gz
I have a scenario that asserts two simple facts, then reads a rule file, then fires the
rules. One of the rules retracts one of the facts, then modifies another object. An NPE
results when things are run as in the attached files.
However, if the rule file is read first, then the facts are asserted, there is no NPE.
Alternatively, if the second rule, the consequence of which retracts one of the facts, is
modified so that the retract is the last statement in the consequence, then the NPE does
not occur, even if the facts are asserted before the rules are read.
--
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