Sanne,
You can think of jBPM as a 'sophisticated' state machine. In most cases a workflow
has the need to keep track of what is going on at a particular moment in time (i.e. manage
state). OTOH pure state machines cannot deal with e.g. multiple concurrent paths of
execution and automatically processed activities. This is the domain where workflow
engines such as jBPM pop up.
Regards,
Koen
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4011865#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...