User development, A new message was posted in the thread "Problem Signaling a Waiting Execution": http://community.jboss.org/message/521222#521222 Author : Ronald van Kuijk Profile : http://community.jboss.org/people/kukeltje Message: -------------------------------------------------------------- Well, jBPM does 'automatically' transition from one node to the other automatically IF the type of node is *not* one that is a wait-state  (state, task and custom, the latter depending on the implementation). All other nodes transition 'automatically'.   Transitioning from a waitstate to the next state is done by a signal from an external system. For that to happen, pass a relevant id (task, execution, activity) to that external system and use it to signal jBPM when the external system is finished. jBPM can never know when this needs to take place. There is one exception. Timers on transitions in wait-states can also advance the execution.   For calling external things, The java node is for simply calling external java classes. If you want more, implement e.g. your own custom node. It's not that difficult and if you take a look at the tests/examples in the source.   Ronald -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/521222#521222