RE: Question about capturing states explicitly in BPEL/BPML

Well, a BPEL engine is a stateful one, in the sense that it keeps track of multiple instances of the process and, for each instance, knows where it is along the process flow. Of course, a BPEL flow has decision points (e.g. switch) and, in order to remember which particular path was taken, you would have to keep track of those choices at the process level (which you can do, as you mention, by using BPEL variables).

Ugo

> -----Original Message-----
> From: public-ws-chor-request@w3.org
> [mailto:public-ws-chor-request@w3.org]On Behalf Of JC Reddy
> Sent: Thursday, December 04, 2003 12:17 PM
> To: public-ws-chor@w3.org
> Subject: Question about capturing states explicitly in BPEL/BPML
> 
> 
> 
> 
> One feature that I really like about Petri-net based workflow 
> modeling is
> the ability to capture states explicitly. For example, if I 
> am passing a
> work item along a workflow, I know what states it has been, 
> and what the
> current state is.
> 
> It is my understanding that both BPEL and BPML doesn't offer 
> that, although
> one can capture the state information using data containers 
> (and such) in
> indirect ways. Any thoughts on this?
> 
> 
> Thanks,
> JC Reddy
> 
>

Received on Thursday, 4 December 2003 15:39:27 UTC