[jboss-user] [jBPM Users] - Re: workflow design about wait states

[kukeltje]

1: Correct

2: No, not necessarily. Yes, with manually firing the jobs and doing nothing in addtion you are right. But... You could always do one of two things if you really think it is important (keep in mind that a fork is 'parallel on the BUSINESS level', not by definition multi-threaded (although sometimes they are processed that way)
- Start a new threads where you manually fire the jobs
- Switch back to the jobExecutor in these case (preferred) with multiple threads (5 is the default afaik)

But as you can read from Jorams post (and what I forgot to explain to you) is that in addition to this you have to make sure the unittest thread is not ended before both jobs are finished and the join is reached. This can be done by one long Thread.sleep(..), or by having a loop which tests if the execution is in a specific state or if it is ended and if not, sleep a short time and test again.


View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4255462#4255462

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4255462