[
https://issues.jboss.org/browse/JBRULES-2771?page=com.atlassian.jira.plug...
]
Mark Proctor resolved JBRULES-2771.
-----------------------------------
Fix Version/s: 5.2.0.M2
(was: 5.2.0.M1)
Resolution: Out of Date
I believe this is fixed. This was becaused named partitions other than default did not
implement TMS. That is no longer true and ALL partitions now use the same codebase. Please
let me know if it's still a bug
NPE in update call from wrong WM Entry Point
--------------------------------------------
Key: JBRULES-2771
URL:
https://issues.jboss.org/browse/JBRULES-2771
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 5.1.1.FINAL
Reporter: Wolfgang Laun
Assignee: Mark Proctor
Fix For: 5.2.0.M2
This sequence of statements disagrees with the documentation:
WorkingMemoryEntryPoint entryPoint = kSession.getWorkingMemoryEntryPoint(
"epn" );
FactHandle fh = entryPoint.insert( fact );
kSession.update( fh, fact ); // should be done using entryPoint.update
But this causes (in 5.1.1) a NPE
Exception in thread "main" java.lang.NullPointerException
at org.drools.common.AbstractWorkingMemory.update(AbstractWorkingMemory.java:1379)
at org.drools.common.AbstractWorkingMemory.update(AbstractWorkingMemory.java:1338)
at
org.drools.impl.StatefulKnowledgeSessionImpl.update(StatefulKnowledgeSessionImpl.java:266)
at event.Main.execute(Main.java:153)
at event.Main.main(Main.java:164)
This is the line:
if ( this.maintainTms ) {
status = ((InternalFactHandle) factHandle).getEqualityKey().getStatus();
}
and similar code can be found in trunk, so I suppose this is still possible.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira