You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fx-dev@ws.apache.org by Sanjesh Pathak <sa...@soapknox.com> on 2007/03/20 16:01:42 UTC
[Sandesha2] Enhancement
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
RE: [Sandesha2] Enhancement
Posted by Gilbert Pilz <Gi...@bea.com>.
During this weeks F2F meeting of the WS-I RSP Working Group it was decided
to add the following requirement to the RSP 1.0 profile:
Rxxx: When sending a CloseSequence or a TerminateSequence, an RM Source
MUST always include LastMsgNumber.
While RSP 1.0 is far from being finished and it is possible that this
requirement may be removed in some later draft of the profile, I note that
there was very no controversy or debate over this issue. In other words, I
would be very surprised if the final RSP 1.0 profile did not contain this
requirement.
- gp
_____
From: Sanjesh Pathak [mailto:sanjesh@soapknox.com]
Sent: Sunday, March 25, 2007 10:10 PM
To: Gilbert Pilz; 'Chamikara Jayalath'
Cc: sandesha-dev@ws.apache.org
Subject: RE: [Sandesha2] Enhancement
Gilbert,
Thanks for this update. Let's wait till this issue is finalized.
Sanjesh
_____
From: Gilbert Pilz [mailto:Gilbert.Pilz@bea.com]
Sent: Wednesday, March 21, 2007 7:48 PM
To: Chamikara Jayalath; Sanjesh Pathak
Cc: sandesha-dev@ws.apache.org
Subject: RE: [Sandesha2] Enhancement
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:chamikaramj@gmail.com]
Sent: Tuesday, March 20, 2007 9:27 PM
To: Sanjesh Pathak
Cc: sandesha-dev@ws.apache.org
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 <sa...@soapknox.com> 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
Re: [Sandesha2] Enhancement
Posted by Chamikara Jayalath <ch...@gmail.com>.
Hi Gilbert,
Oh. Missed that.
Thanks for the info :-)
Chamikara
On 3/22/07, Gilbert Pilz <Gi...@bea.com> wrote:
>
> 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:chamikaramj@gmail.com]
> *Sent:* Tuesday, March 20, 2007 9:27 PM
> *To:* Sanjesh Pathak
> *Cc:* sandesha-dev@ws.apache.org
> *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 <sa...@soapknox.com> 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
> >
> >
> >
> >
> >
>
>
>
RE: [Sandesha2] Enhancement
Posted by Gilbert Pilz <Gi...@bea.com>.
During this weeks F2F meeting of the WS-I RSP Working Group it was decided
to add the following requirement to the RSP 1.0 profile:
Rxxx: When sending a CloseSequence or a TerminateSequence, an RM Source
MUST always include LastMsgNumber.
While RSP 1.0 is far from being finished and it is possible that this
requirement may be removed in some later draft of the profile, I note that
there was very no controversy or debate over this issue. In other words, I
would be very surprised if the final RSP 1.0 profile did not contain this
requirement.
- gp
_____
From: Sanjesh Pathak [mailto:sanjesh@soapknox.com]
Sent: Sunday, March 25, 2007 10:10 PM
To: Gilbert Pilz; 'Chamikara Jayalath'
Cc: sandesha-dev@ws.apache.org
Subject: RE: [Sandesha2] Enhancement
Gilbert,
Thanks for this update. Let's wait till this issue is finalized.
Sanjesh
_____
From: Gilbert Pilz [mailto:Gilbert.Pilz@bea.com]
Sent: Wednesday, March 21, 2007 7:48 PM
To: Chamikara Jayalath; Sanjesh Pathak
Cc: sandesha-dev@ws.apache.org
Subject: RE: [Sandesha2] Enhancement
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:chamikaramj@gmail.com]
Sent: Tuesday, March 20, 2007 9:27 PM
To: Sanjesh Pathak
Cc: sandesha-dev@ws.apache.org
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 <sa...@soapknox.com> 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
Re: [Sandesha2] Enhancement
Posted by Chamikara Jayalath <ch...@gmail.com>.
Hi Gilbert,
Oh. Missed that.
Thanks for the info :-)
Chamikara
On 3/22/07, Gilbert Pilz <Gi...@bea.com> wrote:
>
> 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:chamikaramj@gmail.com]
> *Sent:* Tuesday, March 20, 2007 9:27 PM
> *To:* Sanjesh Pathak
> *Cc:* sandesha-dev@ws.apache.org
> *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 <sa...@soapknox.com> 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
> >
> >
> >
> >
> >
>
>
>
RE: [Sandesha2] Enhancement
Posted by Sanjesh Pathak <sa...@soapknox.com>.
Gilbert,
Thanks for this update. Let's wait till this issue is finalized.
Sanjesh
_____
From: Gilbert Pilz [mailto:Gilbert.Pilz@bea.com]
Sent: Wednesday, March 21, 2007 7:48 PM
To: Chamikara Jayalath; Sanjesh Pathak
Cc: sandesha-dev@ws.apache.org
Subject: RE: [Sandesha2] Enhancement
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:chamikaramj@gmail.com]
Sent: Tuesday, March 20, 2007 9:27 PM
To: Sanjesh Pathak
Cc: sandesha-dev@ws.apache.org
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 <sa...@soapknox.com> 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
RE: [Sandesha2] Enhancement
Posted by Sanjesh Pathak <sa...@soapknox.com>.
Gilbert,
Thanks for this update. Let's wait till this issue is finalized.
Sanjesh
_____
From: Gilbert Pilz [mailto:Gilbert.Pilz@bea.com]
Sent: Wednesday, March 21, 2007 7:48 PM
To: Chamikara Jayalath; Sanjesh Pathak
Cc: sandesha-dev@ws.apache.org
Subject: RE: [Sandesha2] Enhancement
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:chamikaramj@gmail.com]
Sent: Tuesday, March 20, 2007 9:27 PM
To: Sanjesh Pathak
Cc: sandesha-dev@ws.apache.org
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 <sa...@soapknox.com> 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
RE: [Sandesha2] Enhancement
Posted by Gilbert Pilz <Gi...@bea.com>.
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:chamikaramj@gmail.com]
Sent: Tuesday, March 20, 2007 9:27 PM
To: Sanjesh Pathak
Cc: sandesha-dev@ws.apache.org
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 <sa...@soapknox.com> 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
RE: [Sandesha2] Enhancement
Posted by Gilbert Pilz <Gi...@bea.com>.
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:chamikaramj@gmail.com]
Sent: Tuesday, March 20, 2007 9:27 PM
To: Sanjesh Pathak
Cc: sandesha-dev@ws.apache.org
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 <sa...@soapknox.com> 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
RE: [Sandesha2] Enhancement
Posted by Sanjesh Pathak <sa...@soapknox.com>.
Thanks Chamikara for the info. There is no need for that enhancement then.
Sanjesh
_____
From: Chamikara Jayalath [mailto:chamikaramj@gmail.com]
Sent: Tuesday, March 20, 2007 11:27 PM
To: Sanjesh Pathak
Cc: sandesha-dev@ws.apache.org
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 <sa...@soapknox.com> 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
RE: [Sandesha2] Enhancement
Posted by Sanjesh Pathak <sa...@soapknox.com>.
Thanks Chamikara for the info. There is no need for that enhancement then.
Sanjesh
_____
From: Chamikara Jayalath [mailto:chamikaramj@gmail.com]
Sent: Tuesday, March 20, 2007 11:27 PM
To: Sanjesh Pathak
Cc: sandesha-dev@ws.apache.org
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 <sa...@soapknox.com> 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
Re: [Sandesha2] Enhancement
Posted by Chamikara Jayalath <ch...@gmail.com>.
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 <sa...@soapknox.com> 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
>
>
>
>
>
Re: [Sandesha2] Enhancement
Posted by Chamikara Jayalath <ch...@gmail.com>.
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 <sa...@soapknox.com> 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
>
>
>
>
>