Hi Harjot,

In 5.2 we merge the current implementation for Variable Persistence with the core marshaling mechanisms of drools.

You can find a test that show how to configure the new Persisters in the following test inside the jbpm-persistence-jpa project:

https://github.com/droolsjbpm/jbpm/blob/master/jbpm-persistence-jpa/src/test/java/org/jbpm/persistence/session/VariablePersistenceStrategyTest.java

I was responsible for that merge and for the unification of these mechanisms, so please feel free to report any problem that you have with it.

Greetings.

Hey Mauricio,

I was wondering if there were any changes to the behavior of calling:

env.set(EnvironmentName.CMD_SCOPED_ENTITY_MANAGER, myCmdScopedEntityManager);

I seem to get the following stack trace when using this (it worked in the previous release)

SEVERE: [http-thread-pool-8080(2)] ERROR essionCommandService - Could not commit session

java.lang.NullPointerException

    at org.drools.persistence.jpa.JpaPersistenceContext.findWorkItemInfo(JpaPersistenceContext.java:41)

    at org.drools.persistence.jpa.processinstance.JPAWorkItemManager.completeWorkItem(JPAWorkItemManager.java:108)

    at org.drools.command.runtime.process.CompleteWorkItemCommand.execute(CompleteWorkItemCommand.java:69)

    at org.drools.command.runtime.process.CompleteWorkItemCommand.execute(CompleteWorkItemCommand.java:32)

    at org.drools.persistence.SingleSessionCommandService.execute(SingleSessionCommandService.java:292)

    at org.drools.command.impl.CommandBasedStatefulKnowledgeSession$1.completeWorkItem(CommandBasedStatefulKnowledgeSession.java:149)

i encounter the same exception, you can try un-register the JPAWorkingMemoryDbLogger but comment the line:

//new JPAWorkingMemoryDbLogger(ksession);

Hmm that error doens't seem related with the variable persistence strategies.. when are you getting that?

Cheers