Just as Bernd says, control is propagated in a chain of responsibility from node to transition to node until a node stops propagating. The latter node will be the wait state. The call stack is:
node.execute()
| ->node.leave(Transition)
| ->transition.take()
| ->node.enter()
| ->node.execute()
As a side note, in jBPM 3 this simple propagation model has indirect recursion and may result in a stack overflow if a wait state is not encountered soon enough. This has been addressed in PVM.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4162160#4162160
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4162160
anonymous wrote :
| some rumours about a really new wiki.
|
yep, that's supposed to be on the way. However will it really fit our needs? Who knows. Currently we take was has been proven successful for other projects. The foremost reason for the custom mediawiki is that we want to get rid of docbook references at all. It will all be compiled from the wiki, regardless if it's user or developer contribution to the docs.
This leaves us with one source for documentation and eliminates the redundancy between docbook and wiki docs.
And you know: The people only write documentation if it's easy todo so.
That includes maintenance as well.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4162089#4162089
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4162089