Thanks for the reply, Kris.
I figured it might be something like that, but was thrown because one of the
test cases in PersistentStatefulSessionTest (testPersistenceWorkItems3) does
check for process state COMPLETE.
I worked around the issue by adding a ProcessEventListener that implements
the af
Dan,
Once you start using persistence, you should know that the process
instance you are retrieving is no longer the internal process instance
but a version of the process instance at the moment you requested it.
This process instance however is disconnected, meaning that it will not
automati
More info...
This behavior is reproducible in the Drools JPA test cases.
In
org.drools.persistence.session.PersistentStatefulSessionTest.testPersistenceState()
and testPersistenceRuleSet(), if you add a breakpoint before loading the
processInstance the last time (when it is null because the proce
Hi,
I'm seeing some odd behavior in Drools Flow 5.1.1. When using JPA and
creating a StatefulKnowledgeSession using
JPAKnowledgeService.newStatefulKnowledgeSession(), processes look like they
run to completion, but calling RuleFlowProcessInstance.getState() on process
instances created froim this
