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)