Alejandro Guizar [http://community.jboss.org/people/alex.guizar%40jboss.com] 
replied to the discussion

"Is the simple fork/join with async execution paths broken in jBPM 4.0"

To view the discussion, visit: http://community.jboss.org/message/547948#547948

--------------------------------------------------------------
> Can anyone please explain +why+ one needs to put async continuations on each 
> activity within a fork in order for things to advance automatically?
Good question. I've filed  https://jira.jboss.org/browse/JBPM-2888 JBPM-2888 to 
investigate this problem. I'm guessing it is related to  
https://jira.jboss.org/browse/JBPM-2787 JBPM-2787: process instances getting 
stuck in a fork, for jBPM3. There, setting the async attribute +in the join 
node+ is part of the solution. What strikes me as odd reading the comments in 
this thread is that every activity following the fork needs to be made 
asynchronous in jBPM4.

--------------------------------------------------------------

Reply to this message by going to Community
[http://community.jboss.org/message/547948#547948]

Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2034]

_______________________________________________
jboss-user mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/jboss-user

Reply via email to