"burrsutter" wrote : Do you also find the need for synchronous processing within
jBPM? Where the calling thread should be blocked as each node (assumes no wait-states) is
executed and control is returned to the calling thread when the process instance is
Doing this in the current manner is the only way that is guaranteed to work 100% of the
time and scales very well. It also integrates well with transactions, something else that
synchronous invocations of the process is not guaranteed to do.
In general you do not know how jBPM will choose to control the process flow. Any action
within the process instance can choose to defer processing, whether it is through async,
timers, human intervention, invoking ESB services or other possibilities. It just takes
one of these to break the integration you are suggesting.
View the original post :
Reply to the post :