February 2009 - jbpm-dev - Jboss List Archives

[Design of JBoss jBPM] - Re: process definition as a resource

by heiko.braun＠jboss.com

nobody will rename the classes. but you'd need to rename the deployment artifact (i.e. myProcess_v2.par). Otherwise you'd force redeployment of an existing deployment artifact. But the then it works like Bernd says, the scoping is guaranteed by the classloading/deployer framework. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4211266#4211266 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4211266

15 years, 9 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: process resume

by kukeltje

This is a topic for the user forum.. But imo the solution would be to not persist the process instance in the exceptionhandler. That way it would be the same as before the exception (a rollback) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4211171#4211171 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4211171

15 years, 9 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Add jBPM performance test coverage

by thomas.diesler＠jboss.com

What about these tests here http://jbpm.dyndns.org:8280/hudson/job/jBPM3-JDK1.5/lastBuild/testReport/... are they related to performance testing? Looking at the code it is not obvious. What does this package stand for? | org.jbpm.perf | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4211168#4211168 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4211168

15 years, 9 months

1
0
0 / 0

[Design of JBoss jBPM] - process resume

by galanfish

in a parallel structure for example and-split -> and-join scene, more than one child-execution will be created, if something goes wrong in alternative branch with a exception throw out, in the exceptionhandler i persist the process instance, is it possible to resume the process instance to the status before the exception happen, i mean just what it looks like as the moment the exception still haven't happen, i wanted to redo the logic or what programmic should i do to resolve this problem View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4211119#4211119 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4211119

15 years, 9 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: task and swimlane roles

by kukeltje

I will come up with a more detailed response later, but why not take terminology from http://www.workflowpatterns.com/patterns/resource/resource_modelling.php or maybe from ws-ht? Creating our own terminology is imo not the way to go. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4211096#4211096 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4211096

15 years, 9 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: statefull vs stateless delegation classes

by jbarrez

I agree: they should be stateless. And indeed, as a consequence they can be shared by all who needs them. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4211095#4211095 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4211095

15 years, 9 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: statefull vs stateless delegation classes

by tom.baeyens＠jboss.com

"camunda" wrote : But it should be made sure that one action object is only used for one thread at a time, like a pool... why ? if they're stateless, i don't see the point. then all threads can use the same delegation object, no ? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4211094#4211094 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4211094

15 years, 9 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: statefull vs stateless delegation classes

by camunda

I think it is good practice to keep them stateless as. I also don't remember cases where it is not true. And it doesn't make sense, since you cannot access the changed state later. But it should be made sure that one action object is only used for one thread at a time, like a pool... And it must be documented somewhere ;-) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4211085#4211085 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4211085

15 years, 9 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: statefull vs stateless delegation classes

by kukeltje

40 classes that is, not years ;-) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4211080#4211080 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4211080

15 years, 9 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: statefull vs stateless delegation classes

by kukeltje

I've looked through all the delegation classes I've made the last few years (around 40) and none of them update any member fields. But that is just me (and probably more by accident then on purpose).... not sure if it is save to assume everybody did this... View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4211079#4211079 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4211079

15 years, 9 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