[jboss-jira] [JBoss JIRA] Created: (JBPM-1015) ProcessLogs that represent changes of process intance that take place within Timer.Execute are not saved in DB

[Gil Messerman (JIRA)]

ProcessLogs that represent changes of process intance that take place within Timer.Execute are not saved in DB
--------------------------------------------------------------------------------------------------------------

                 Key: JBPM-1015
                 URL: http://jira.jboss.com/jira/browse/JBPM-1015
             Project: JBoss jBPM
          Issue Type: Bug
          Components: Core Engine
    Affects Versions:  jBPM jPDL 3.2.1
         Environment: Tomcat 5.0.28 or Jboss
            Reporter: Gil Messerman
         Assigned To: Tom Baeyens


It seems to be a problem with Timer implementation. When some change in process occurs (such as transition or action call), the process instance should be added to jbpmContext to the list of auto saved process instances (actual saving occurs when JBPMContex.close() is called). Apparently Timer.execute does not do it and as a result, the log of all operations performed by Timer.execute is not stored in DB and getting lost. 

To fix the problem, the token.getProcessInstance() should be added to "autoSaveProcessInstances" list in JBPMContext.


-- 
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