OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ws-tx message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: NEW Issue: WS-AT: Define meaning/use of CurrentContext


Issue name -- WS-AT: Define meaning/use of CurrentContext

PLEASE DO NOT REPLY TO THIS EMAIL OR START A DISCUSSISON THREAD UNTIL 
THE ISSUE IS ASSIGNED A NUMBER.

The issues coordinators will notify the list when that has occurred.

Target document and draft:

Protocol:  WS-AT

Artifact:  spec

Draft:

WS-AT CD 0.1 uploaded

Link to the document referenced:

http://www.oasis-open.org/apps/org/workgroup/ws-tx/download.php/17325/wstx-wsat-1.1-spec-cd-01.pdf

Section and PDF line number:

New section required


Issue type:

Editorial


Related issues:

Issues 018 - 021, relating to meaning of CurrentContext


Issue Description:

Make precise statement on meaning (for WS-AT) of 
/CreateCoordinationContext/CurrentContext.


Issue Details:

WS-AT should state purpose and meaning of 
/CreateCoordinationContext/CurrentContext. The WS-C statement is very 
general.


Proposed Resolution:

The attached Word document 
(2006-03-21.Guaranteeing.Atomicity.of.Transaction.Tree.doc) contains a 
new section that a) defines the behaviour I deduce is intended and b) 
avoids stating whether a lazy or eager registration approach is taken 
(treating that as an implementation issue).

MS-Word document



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]