RE: [wsbpel] Issue 53 - Motion for consideration by the TC

["Yaron Goland" <ygoland@bea.com>]

Issues 53-59 only address global scope compensation and only in the case of
an external message sent in the context of a distributed transaction
protocol.

BPEL's compensation handlers are available at all scopes and cover all types
of compensation triggers not just external messages from distributed
transaction protocols.

So clearly Issue 53-59 cannot substitute, as you suggest below, for BPEL's
existing compensation mechanism.

Regarding your question on (b), I can speak for my customers in saying that
cascading compensations happen all the time in their Web Services. That is,
an event triggers compensation inside a Web Service which then causes a
cascading set of compensations to occur in the Web Service.

The problem is that this design pattern has to be implemented by hand, which
is extremely challenging. However, having seen this design pattern for many
years in Web Services we now have sufficient experience to design an
optimization to make matters simpler, this is where the cascading
compensation features in BPEL come from.

For reasons previously stated similar experience is lacking with distributed
transactions which, again, is why the optimizations in issues 53-59 are
premature and hence should not be adopted.

		Yaron


> -----Original Message-----
> From: Haugen Robert [mailto:Robert.Haugen@choreology.com]
> Sent: Tuesday, January 13, 2004 11:41 AM
> To: wsbpel@lists.oasis-open.org
> Subject: RE: [wsbpel] Issue 53 - Motion for consideration by the TC
> 
> 
> Yaron Goland wrote:
> 
> > The BPEL group has a vast vein of experience to mine 
> > in creating a simplified local compensation framework 
> > as customers have been implementing local compensation 
> > handlers on every Web Service product and platform 
> > since the dawn of web services. 
> 
> Do you mean:
> 
> (a) simple local undos per Web service?
> 
> or
> 
> (b) cascading Compensations with nesting and links as in BPEL?
> 
> I don't think (a) qualifies as experience with (b).
> 
> Moreover, I think local undos can fit into a business transaction
> framework such as we're proposing, as easily (maybe more easily) than
> they fit into the BPEL cascading Compensations.
> 
> To unsubscribe from this mailing list (and be removed from 
> the roster of the OASIS TC), go to 
> http://www.oasis-open.org/apps/org/workgroup/wsbpel/members/le
> ave_workgroup.php.
> 
>

<<attachment: winmail.dat>>