[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: New proposed issues 12/15 - 1/4
Three new issues sent in since the
F2F listed below. Please let me and the list know if any were missed. Regards,
Marc g Proposed-01 Title: Level of "response message" unclear, for SequenceResponse. Proposed-02 Title: Fault Meswsages for
Terminated Sequence Proposed-03 Title: Can CreateSequenceResponse, CloseSequenceResponse, and TerminateSequenceResponse be sent on Soap Request
Proposed-01 Title: Level of "response message" unclear, for SequenceResponse. Origin: http://lists.oasis-open.org/archives/ws-rx/200512/msg00155.html Description: The wsrm specification makes several mentions of carrying
some operation messages (CreateSequenceResponse, CloseSequenceResponse) over
"response messages". It is unclear whether these are underlying protocol
responses if a 2-way protocol is used, or are SOAP responses (as in SOAP MEPs), or are just
RM-level messages with "response" semantics. Justification: In order to remain independent from underlying protocol
bindings, and to not preclude future SOAP bindings to other protocols, (or even other
HTTP bindings such as PAOS) the specification must not make any assumption about MEPs
that take place below SOAP level. The current wording could be interpreted as: a
request-response underlying protocol is in use and messages such as CreateSequenceResponse bind to a
response. Target: core Proposal: Reword "request message" and "response
message" so that they become respectively SOAP request and SOAP response messages (either referring
to SOAP responses as informally Defined in SOAP 1.1 or to SOAP Request-response MEP
formally defined in 1.2). Replace the expression
"request-response pattern" (Section 4) by SOAP request-response MEP. Proposed-02 Title: Fault Meswsages for
Terminated Sequence Origin: Tom Rutt http://lists.oasis-open.org/archives/ws-rx/200601/msg00001.html
Description: It is not clear whether
"SequenceTerminated" Fault is allowed in response to a message with a
terminated sequence ID. Justification: RMS implementations need to know
what fault messages to expect if a message is sent with a terminated Sequence
ID. It is unclear whether
"SequenceTerminated" may be used in response to a message sent with a terminated
sequence ID. If the RMD knows that a sequence ID was terminated, it could
convey extra information by sendint the "SequencdTerminated" Fault. Target: core Proposal: Add the following clarification to
the text regarding sequence Termination" "Either a
"SequenceTerminated" fault or an "UnknownSequence" fault
may be returned by an RMD in response to a messaged containing a terminated
Sequence ID." Proposed-03 Title: Can CreateSequenceResponse, CloseSequenceResponse, and TerminateSequenceResponse be sent on Soap Request
Origin: Tom Rutt http://lists.oasis-open.org/archives/ws-rx/200601/msg00002.html
Description:
The WSDL description in Annex C imply that CreateSequenceResponse, CloseSequenceResponse, and TerminateSequenceResponse are output messages for three WSDL request/response operations.
However, it was stated at the Face to Face meeting in these can be send in a soap request targeted at a ReplyTo Epr sent in the associated request message.
Justification:
The specification needs to clarify that the create sequence , close sequence, and terminate sequence operations are not necessarily wsdl request/response operations.
Target: core
Proposal:
Add the following sentence to annex C:
"In this annex the WSDL descriptions for the sequence operations are specified as WSDL request/response operations.
However, if WS-addressing is in use, the responses to these operations may be sent in the body of a soap request targeted at a ReplyTo epr included in the soap message carrying the operation request."
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]