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

[mmusaji]

This was my original problem... in real world I wont know how long to sleep for. I need to read the objects back but only once they have all been updated after a certain amount of time (which could be 2 seconds or 20 seconds).

When I use take("join"), I get org.jbpm.api.JbpmException: there is no transition join in activity(validate red request). But there is.

I use takeDefaultTransition() (no sleep in my unit test) I get StaleObjectStateException because my unit test and my workflow are out of sync. This was pointed out my JBarrez in one of my previous posts. The sleep in my unit test solved this problem.

If I don't use continue="exclusive" in the join, then my workflow doesn't continue past the join... just stops.

Do you know how the waitForSignal() and takeDefaultTransition() methods are affected (if at all) when used async? Using them normally like in the examples they work fine.

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

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