Re: [ws-rx] Possible new issue: identifier in CloseSequenceResponse message

[Doug Davis <dug@us.ibm.com>]

I think the only reason I didn't include
an ID in the CloseResponse was because I assumed the wsa:relatesTo would
take care of it and it seemed like redundant information.  I agree
we should be consistent and I don't have a huge preference either way.
-Doug

Anish Karmarkar <Anish.Karmarkar@oracle.com>

02/02/2006 07:16 PM

To	wsrx <ws-rx@lists.oasis-open.org>
cc
Subject	[ws-rx] Possible new issue: identifier in CloseSequenceResponse message

While creating the proposal for TerminateSequenceResponse
message, I 
noticed that the CloseSequenceResponse message does not have the 
Sequence Identifier in the message. Is this an an oversight and that the
identifier does indeed need to be included in the message OR is the 
intention to rely on wsa:RelatesTo? I think having the identifier in the
message just makes it much cleaner/simpler/consistent. But regardless,
I 
included the identifier in the TSR message (assuming that it was an 
error not to include it in the CloseSequenceReponse message -- possibly
an incorrect assumption) and we need to be consistent: either have the
Identifier in the CloseSequenceResponse message or remove the Identifier
in the TerminateSequenceResponse message.

I should have highlighted this in my proposal for the TSR message. I 
intended to, but somehow missed it. Apologies.

-Anish
--