Chamikara, This was true up until fairly recently. The resolution to WS-RX PR i022 added LasMsgNumber elements to the CloseSequence and TerminateSequence messages. While the WS-RX TC is still in the process of moving to CS with these (and obviously other) changes, there are no issues around these features. In other words, it is a good bet that they will be in the final OASIS standard. While the phrasing of the spec says that the RMS SHOULD add the LastMsgNumber to any CloseSequence or TerminateSequence messages it sends, it is possible that the WS-I RSP 1.0 profile will tighten the requirement to a MUST (stay tuned for updates). - gp
_____ From: Chamikara Jayalath [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 20, 2007 9:27 PM To: Sanjesh Pathak Cc: [email protected] Subject: Re: [Sandesha2] Enhancement Hi Sanjesh, In WSRM 1.0 it's possible to know this by observing the wsrm:Sequence header. In WSRM 1.1 there is not concept of a LastMessage. Chamikara On 3/20/07, Sanjesh Pathak <[EMAIL PROTECTED]> wrote: Hi, Can someone please put this property into the Axis2 MessageContext from inside Sandesha2: Property name: Sandesha2Constants.MessageContextProperties.IS_LAST_MESSAGE Value: Boolean So we can access this property from inside Axis2. This is similar to the other Sandesha2 (version 1.1) properties we currently can access from Axis2 MessageContext: Sandesha2Constants.MessageContextProperties.MESSAGE_NUMBER Sandesha2Constants.MessageContextProperties.SEQUENCE_ID Thank you, Sanjesh Real-Time Web Service Monitoring for Java and .NET SoapKnox Inc http://www.soapknox.com Ph: 832 279 3745
smime.p7s
Description: S/MIME cryptographic signature
