Re: [wsbpel] Issue - 53 - Should include Business Transaction Management (BTM) programming constructs compatible with WS-T, BTP and WS-TXM

["Mark Little" <mark.little@arjuna.com>]

I agree that something like this is required. However, I see several problems with the approaches outlined in the document:

 

"These facilities are all portable over products implementing WS-T BA, BTP and WS-TXM outcome protocols."

 

This is only true if you take a subset of the protocols defined by WS-T and WS-TXM *and* consider those specifications to be closed. Both WS-TXM and WS-T are "live" documents in that other protocols may be added to them over time, and these protocols may not be two-phase. I know it's not possible to plan for the unknown, but even the current notion within WS-T and WS-TXM of a do-undo interaction for compensators doesn't require explicit two-phase support at the protocol level.

 

"The WS-Coordination specification (proprietary consortium, August 2002) is able to support context passing for multiple coordination protocols, and its use will support the goal of compatibility with WS-T, BTP and WS-TXM"

 

WS-Context would seem more relevant because it is solely about context and does not require a coordinator in order to create a basic context (which WS-C does). I know at the moment that's also a proprietary consortium, so this is a more tricky call to make.

 

Mark.

----- Original Message -----

From: ws-bpel issues list editor

To: wsbpel@lists.oasis-open.org

Sent: Wednesday, August 27, 2003 12:00 AM

Subject: [wsbpel] Issue - 53 - Should include Business Transaction Management (BTM) programming constructs compatible with WS-T, BTP and WS-TXM

This issue has been added to the wsbpel issue list. The issues list is posted as a Technical Committee document to the OASIS WSBPEL TC pages on a regular basis. The current edition, as a TC document, is the most recent document with the title in the "Issues" folder of the WSBPEL TC document list - the next posting will include this issue. The list editor's working copy, which will normally include an issue when it is announced, is available at this constant URL.

Issue - 53 - Should include Business Transaction Management (BTM) programming constructs compatible with WS-T, BTP and WS-TXM

Status: open
Date added: 26 Aug 2003
Origin: Choreology submission on business transaction management (document details), issue A
Submitter: Alastair Green
Date submitted: 26 August 2003
Description: There are three multi-vendor specifications which address the needs of business transaction management for Web Services: Business Transaction Protocol 1.0 (OASIS Committee Specification, June 2002); WS-Transaction (proprietary consortium, August 2002), and the very recently published WS-TXM (proprietary consortium, August 2003).

In our view BTP Cohesions, WS-T Business Activity, and WS-TXM Long-Running Actions are the most relevant aspects of these specifications for WS-BPEL. These aspects overlap to a very high degree, each effectively utilizing a two-phase (promise/decide) outcome protocol. (We should emphasize that there has been little time to analyze or assimilate WS-TXM, so this is a provisional conclusion with respect to that specification).

WS-BPEL should be equipped with the ability to create and terminate business transactions, and to define process participation in such transactions, in a way which is compatible with the intersection of these three capabilities. This will minimize dependence on future standardization efforts in the BTM area.
Submitter's proposal: Syntax should be added to WS-BPEL to permit

1. Business transaction creation, manifested by the creation of a business transaction context variable.

2. Business transaction context reception and transmission (propagation) via invoke/receive/reply, allowing sub-transaction or pass-through behaviour.

3. Process involvement in business transactions as participants, which can handle positive and negative transaction finalization messages (by means of confirm and cancel handlers).

4. Two-phase termination of business transactions by selection of participants to be prepared, to be cancelled and to be confirmed.

These facilities are all portable over products implementing WS-T BA, BTP and WS-TXM outcome protocols.

The WS-Coordination specification (proprietary consortium, August 2002) is able to support context passing for multiple coordination protocols, and its use will support the goal of compatibility with WS-T, BTP and WS-TXM.
Changes: 26 Aug 2003 - new issue

---

To comment on this issue, please follow-up to this announcement on the wsbpel@lists.oasis-open.org list (replying to this message should automatically send your message to that list), or ensure the subject line as you send it starts "Issue - 53 - [anything]" or is a reply to such a message.

To add a new issue, see the issues procedures document.

To unsubscribe from this list, go to http://www.oasis-open.org/apps/org/workgroup/wsbpel. Note:unsubscribing will result in your withdrawal from this OASIS Technical Committee.