[JBoss-user] [JBoss jBPM] - Re: Doubt canceling a timer and killing the tasks

2006-02-23 Thread boerse
Hi Alex I've just noticed you are right and the token leaves the node 3 times, but does it represent a problem or a serious mistake? I think this way it just works and for the statistics (i'll have to make in the future) it does not affect since only the no-default nodes are taken (acept/cancel

[JBoss-user] [JBoss jBPM] - Re: Doubt canceling a timer and killing the tasks

2006-02-22 Thread [EMAIL PROTECTED]
Neat, I overlooked the end-tasks attribute. I just applied your suggestion and the tests pass. However, if you see the log, you will notice there is a problem in the timeout scenario. Ending the tasks (by virtue of end-tasks="true") results in the token taking the default transition. After that,

[JBoss-user] [JBoss jBPM] - Re: Doubt canceling a timer and killing the tasks

2006-02-22 Thread boerse
Hi Alex! Thanks a lot, today i've been pretty busy developing and i did that a little different: i have 1 timer and 2 actors in a node (each with a task) and i want to keep on the flow as soon as timer expires or any of the actors perform his action. I set a default transition for all to a nop

[JBoss-user] [JBoss jBPM] - Re: Doubt canceling a timer and killing the tasks

2006-02-22 Thread [EMAIL PROTECTED]
Your use case is, in practice, Van der Aalst's deferred choice pattern. I found it interesting and worked it out. Take a look in the jBPM Wiki for the solution I found. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3925705#3925705 Reply to the post : http:/