[jbpm-dev] Re: Removed Timer/autosave in Revision 4006?
Hi Bernd,
While working on JBPM-2036, I noticed that the addAutoSaveToken call was
duplicated in all job classes, so I moved it to JobExecutorThread. Now
that you mention it, the code should be added to ExecuteJobCommand as
well.
Since no test failed, I assumed the net effect was the same. I guess it
broke something on your side. Care to tell me how to reproduce?
-Alejandro
El vie, 27-02-2009 a las 16:02 +0100, Bernd Rücker escribió:
Hi Alex!
With Revision 4006 you removed the fix for
https://jira.jboss.org/jira/browse/JBPM-1015 from the Timer class,
basically this code:
public boolean execute(JbpmContext jbpmContext) throws Exception {
// add processInstance to autoSave field (For details refer to
// https://jira.jboss.org/jira/browse/JBPM-1015)
jbpmContext.addAutoSaveToken(token);
Was this by accident? Or what rational was behind this? Can I
re-include it?
Because now, Bug 1015 would occur again with jbpm 3.2.6…
Thanks
Bernd
EJB-3-Buch: http://www.ejbbuch.de/
Unsere Seminare: http://www.camunda.com/seminare/
Blog: www.bpm-guide.de
---------------------------------------------
camunda services GmbH - The Business Process Company
Werastraße 18 - 70182 Stuttgart
www.camunda.com - info(a)camunda.com
---------------------------------------------
Bernd Rücker
Geschäftsführer
Telefon +49 711 3278645
Mobil +49 171 1473461
bernd.ruecker(a)camunda.com
---------------------------------------------
Amtsgericht Charlottenburg: HRB 113230 B
Geschäftsführer: Jakob Freund, Bernd Rücker
---------------------------------------------