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: Re: [ws-tx] Issue 108 - Other Editorial Issues Surrounding AI#0057 Reviewfor RFC 2119 (I#097), Submission 2


 > 1. Section 2. Proposed by Wilkinson
> The Atomic Transaction coordination context MUST flow on all 
> application  messages involved with the transaction.
> Change proposed in Line 145: Change "must" to "MUST".
> 
> >>Comment: In this section, this is insufficiently defined to 
> propose a requirement. The specification has not yet defined how an 
> "application message is involved in a transaction". This concept is 
> not normatively introduced until Section 4.2. Appropriate normative 
> statement is made on lines 267-269 on conditions that a AT 
> coordination context flows with a
> request message.

This part of this issue is addressed by issue 106 which proposes that the 
text be modified to read:

"The Atomic Transaction coordination context flows in application messages 
involved with the transaction and MUST be represented in 
CoordinationContext format as described in WS-Coordination [WSCOOR]. For 
application messages that use a SOAP binding the CoordinationContext MUST 
flow in the SOAP header of the message."

Andy


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