Overview / Example

Tom,

In the overview of jBpm, you describe that jBpm maintains the state:  
"After loading the process archive, users or systems perform single steps 
of the process. jBpm maintains the state, logs and performs all automated 
actions."

I've written several user-based document-centric workflow applications, 
and in my experience the *state* moves around with the document, and the 
combination of a request and a state into a state machine influences the 
resulting state of the document.  The workflow definition does not have 
any state per se, except what should be accomplished through the workflow. 
 Since jBpm is generic, I don't suspect (or expect) that it takes care of 
handling this persistence--I would think that this would be better left to 
a db of some sort (xml or otherwise).

Can you help me understand what you mean by "maintains the state"a bit 
more, or point me to somewhere?

Thanks,
Brian


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click