February 2009 - jbpm-dev - Jboss List Archives

[Design of JBoss jBPM] - Re: Removed Timer/autosave in Revision 4006?

by camunda

so what is in jbpm 3.2.6? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4213963#4213963 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4213963

15 years, 10 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Removed Timer/autosave in Revision 4006?

by alex.guizar＠jboss.com

anonymous wrote : I always experience a bit confusion of the people about the "forUpdate" methods. And you can forget to use them. Much easier is that is hidden and done automatically... Agreed. Something to watch for in jBPM 4. In version 3, that is how things are... anonymous wrote : introducing the xxxForUpdate on the JbpmContext seems like the second best option for me (and consistent with other jbpm stuff). In the end I decided against it in 3.2.6, because we are about to release. I'll dig on this a bit more in 3.2.7. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4213962#4213962 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4213962

15 years, 10 months

1
0
0 / 0

jbpm-3.2.6.GA QA branch created

by Thomas Diesler

Hi Folks, I created the jbpm-3.2.6.GA QA branch https://svn.jboss.org/repos/jbpm/jbpm3/branches/jbpm-3.2.6.GA/ The Hudson QA is here http://jbpm.dyndns.org:8280/hudson/job/jBPM326-Container-Matrix/ http://jbpm.dyndns.org:8280/hudson/job/jBPM326-Database-Matrix/ Please only commit stuff that fixes regression. cheers -thomas

15 years, 10 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Removed Timer/autosave in Revision 4006?

by camunda

anonymous wrote : except that loadJob could also be used under contexts that do not require saving the process instance But does this harm or break anything? I always experience a bit confusion of the people about the "forUpdate" methods. And you can forget to use them. Much easier is that is hidden and done automatically... But introducing the xxxForUpdate on the JbpmContext seems like the second best option for me (and consistent with other jbpm stuff). anonymous wrote : Perhaps we could meet on your way back?. Bummer. No, I fly back from Cancun and don't return to Mexico City (only for transit in the plane). Next time ;-) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4213920#4213920 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4213920

15 years, 10 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Removed Timer/autosave in Revision 4006?

by alex.guizar＠jboss.com

"camunda" wrote : In my case, we have an own ExecuteJobCommand, since we do some additional stuff. So I had to change that as well to get the Tests green. Maybe other people do the same stuff? Yes, the Seam integration also uses a custom job executor and they may rely on the jobs autosaving the process instance. "camunda" wrote : Couldn't we move this to the JobSession.loadJob() method? Now we have to spread this logic to JobExecutor, ExecuteJobCommand's and so on. Seems like a good proposal, except that loadJob could also be used under contexts that do not require saving the process instance (e.g. a monitoring console). I have the following two proposals: 1. Introduce a loadJobForUpdate method, possibly in JbpmContext (since no XxxSession has any xxxForUpdate method). 2. Forget about it, and just revert. I'm leaning towards (1). Any thoughts? "camunda" wrote : I fly to Mexico next week. Maybe we could just meet for beer on around Tuesday 10.03. in Mexico City? Crap, what a bad coincidence. Right now I'm in Houston, USA, and will be back to Mexico City by March 14th. Perhaps we could meet on your way back? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4213906#4213906 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4213906

15 years, 10 months

1
0
0 / 0

Removed Timer/autosave in Revision 4006?

by Bernd Rücker

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/> http://www.ejbbuch.de/ Unsere Seminare: <http://www.camunda.com/seminare/> http://www.camunda.com/seminare/ Blog: <http://www.bpm-guide.de/> www.bpm-guide.de --------------------------------------------- camunda services GmbH - The Business Process Company Werastraße 18 - 70182 Stuttgart <http://www.camunda.com/> www.camunda.com - <mailto:info@camunda.com> info(a)camunda.com --------------------------------------------- Bernd Rücker Geschäftsführer Telefon +49 711 3278645 Mobil +49 171 1473461 <mailto:bernd.ruecker@camunda.com> bernd.ruecker(a)camunda.com --------------------------------------------- Amtsgericht Charlottenburg: HRB 113230 B Geschäftsführer: Jakob Freund, Bernd Rücker ---------------------------------------------

15 years, 10 months

2
2
0 / 0

[Design of JBoss jBPM] - Removed Timer/autosave in Revision 4006?

by camunda

Bernd wrote : | > 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: | > 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 | Alejandro wrote : | 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? | Hi Alex. Couldn't we move this to the JobSession.loadJob() method? Now we have to spread this logic to JobExecutor, ExecuteJobCommand's and so on. In my case, we have an own ExecuteJobCommand, since we do some additional stuff. So I had to change that as well to get the Tests green. Maybe other people do the same stuff? And in JobSession it would be nice, since then it is "close" to the code handling persistence, or not? Remarks? @Ronald: Yeah, I see a slight chance, that it was missed to write a test for executing jobs via Command ;-) Cheers Bernd P.S @Alex: I fly to Mexico next week. Maybe we could just meet for beer on around Tuesday 10.03. in Mexico City? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4213877#4213877 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4213877

15 years, 10 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Services -changed from List to Set

by camunda

Perfect, thanks! View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4213870#4213870 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4213870

15 years, 10 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Job.configuration property

by camunda

I think too. But I would keep it and just add a javadoc. It is quite handy if you need to store something together with the Job. And in this case you can just exchange the hibernate mapping in your project... View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4213868#4213868 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4213868

15 years, 10 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Job.configuration property

by alex.guizar＠jboss.com

No, must be a legacy artifact. It is not persisted, so its value is kinda limited from my point of view. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4213819#4213819 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4213819

15 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

jbpm-dev February 2009