Kazam,
You are partly right. If you use the async functionality, the signal behaviour
that puts the token from one node into the next will be broken into two
transactions instead of one. The first transaction will put a message on a
message queue (the default jbpm messaging system out of the bo
Thanks Roland that clarifies everything pretty much.
anonymous wrote :
| Could you elaborate on this? Besides the async continuations, jBPM runs in
the client thread (e.g. the webapp, fat client or whatever). It is a library,
not a full separate server
|
Am I correct in saying that,
Und
"kazam" wrote :
| My perhaps silly question is that why isn't async used for Tasks, I have
used Oracle BPEL Workflow before and Tasks response or completion used to be
asynchronous having a callback association in the process when the Task was
completed.
Simple, jBPM has (human) task functi
