ws-rx message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: issue i108 proposal revised
- From: Christopher B Ferris <chrisfer@us.ibm.com>
- To: WS-RX TC <WS-RX_TC@us.ibm.com>
- Date: Wed, 5 Apr 2006 15:08:30 -0400
As per my AI, I have noodled on this
with Anish, Gil and Doug and have come up with the following
revised proposal for i108 [1]
When the processing of an RM protocol header block (with the exception
of Sequence) generates
a fault, and the purpose of the containing message is not exclusive
to that RM protocol header
block, then the receiving endpoint MUST continue normal processing
of the message unless
the generated fault is a SOAP MustUnderstand fault.
Gil had suggested that we add to the glossary a set of terms that could
help us in describing
certain types of messages. I agree. Here's a start:
Sequence lifecycle messages:
A message that contains one of: CreateSequence,
CreateSequenceResponse, CloseSequence, CloseSequenceResponse,
TerminateSequence, TerminateSequenceResponse
as the child element of the soap:Body element.
RM protocol header blocks:
Sequence, SequenceAcknowledgement, AckRequested
Sequence messsage:
A message that contains a Sequence RM prototcol
header block.
Acknowledgement message:
A message that contains a SequenceAcknowledgement
RM protocol header block
[1] http://docs.oasis-open.org/ws-rx/issues/ReliableMessagingIssues.xml#i108
Christopher Ferris
STSM, Software Group Standards Strategy
email: chrisfer@us.ibm.com
blog: http://www.ibm.com/developerworks/blogs/dw_blog.jspa?blog=440
phone: +1 508 377 9295
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]