ws-tx message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Re: [ws-tx] Issue 075 - WS-BA: Sub-coordination undefined
- From: Thomas Freund <tjfreund@us.ibm.com>
- To: ws-tx@lists.oasis-open.org
- Date: Wed, 30 Aug 2006 18:41:36 -0500
Proposed text revision for Issue 075 ... Regards, Tom
1. After line 147 (add)
Business Activity builds on WS-Coordination, which defines an activation and a registration service. Example message flows and a complete description of creating and registering for coordinated activities is found in the WS-Coordination specification [WSCOOR].
The Business Activity coordination context must flow on all application messages involved with the transaction.
Business Activity adds the following semantics to the CreateCoordinationContext operation on the activation service.
- If the request includes the CurrentContext element, the target coordinator is interposed as a subordinate to the coordinator stipulated inside the CurrentContext element.
- If the request does not include a CurrentContext element, the target coordinator creates a new transaction and acts as the root.
2. Move lines 152-155 after the above inserted text
A coordination context may have an Expires attribute. This attribute specifies the period, measured from the point in time at which the context was first received, after which a long-running activity may be terminated solely due to its length of operation. A participant could terminate its participation in the long running activity using the Exit protocol message.
"Ram Jeyaraman" <Ram.Jeyaraman@microsoft.com>
"Ram Jeyaraman" <Ram.Jeyaraman@microsoft.com>
06/30/2006 04:19 PM
|
|
This is identified as WS-TX issue 075.
Please ensure follow-ups have a subject line starting "Issue 075 -
WS-BA: Sub-coordination undefined".
-----Original Message-----
From: Alastair Green [mailto:alastair.green@choreology.com]
Sent: Friday, June 30, 2006 1:40 AM
To: ws-tx@lists.oasis-open.org
Subject: [ws-tx] NEW ISSUE: WS-BA: Sub-coordination undefined
Issue name -- WS-BA: Sub-coordination undefined
PLEASE DO NOT REPLY TO THIS EMAIL OR START A DISCUSSISON THREAD UNTIL
THE ISSUE IS ASSIGNED A NUMBER.
The issues coordinator will notify the list when that has occurred.
Target document and draft:
Protocol: WS-BA
Artifact: spec
Draft: BA spec cd 2
Link to the document referenced:
http://www.oasis-open.org/committees/download.php/18819/wstx-wsba-1.1-sp
ec-cd-02.doc
Section and PDF line number: Section 2, "Using WS-Coordination"
Issue type: Design/Editorial
Related issues:
Issue Description:
Meaning of creating a new context against an existing, current context
is not described or defined.
Issue Details
WS-C places responsibilty on referencing specs to define meaning of use
of current context in CreateCoordinationContext. BA is currently silent
on this.
Proposed resolution
Define meaning of interposition for atomic and mixed outcomes.
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]