I guess there is a question tho... which is whether an application might want to use an RM or SC context as the session mechanism for a service instead of a SOAPSession. Since the SOAPSession approach is not fully defined by any standard (and therefore not guaranteed to interoperate), a user might wish to use RM or SC contexts.
Maybe we should define a pluggable way of defining context in MessageReceivers. I'm just thinking aloud here... there might be issues I haven't yet thought of. Paul On 10/1/06, Jaliya Ekanayake <[EMAIL PROTECTED]> wrote:
Hi Tijs, I don't think SOAP session support is a requirement that can be expected from RM. Sandesha's task ends at the QoS level and what you need is application sessions. The best approach you can use is to write your own message receiver which handle IN, IN... IN OUT message exchange pattern. So this receiver simply will not send a respones at each input message rather will send it at the desired point. Thanks, -Jaliya ----- Original Message ----- From: <[EMAIL PROTECTED]> To: <[email protected]> Sent: Sunday, October 01, 2006 11:19 AM Subject: Re: Re: [Sandesha2] InOrder assurance > Hi Chamikara, > > Thanks for the information. > What I would like is soapsession support, but that seems not to be working > with Reliable Messaging. > The soapsession could then last for the whole sequence. > Is it possible to have a combination of Sequence and soapsession support? > > Thanks, > > Tijs > >> >> van: "Chamikara Jayalath" <[EMAIL PROTECTED]> >> datum: 2006/10/01 Sun AM 08:11:28 MEST >> aan: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> >> cc: [email protected] >> onderwerp: Re: [Sandesha2] InOrder assurance >> >> Hi Tijs, >> >> The lifetime of the service instance depends on ur service scope. The >> default scope is 'Request scope' causing a service instance to be created >> per each request. In your case the service scope hs to be changed to >> 'application' causing a single service instance to be present for the >> whole >> lifetime of the Axis2 system. >> >> To change the scope edit your services.xml file as follows. >> >> <service name="Service1" scope="application"> >> </service> >> >> More info. can be found in following article by Deepal, >> http://www.developer.com/services/article.php/3620661 >> >> Chamikara >> >> On 10/1/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: >> > >> > Hi there, >> > >> > I have a question/remark about the working of the InOrder QOS for >> > Sandesha2. I am working on a scenario where I want to sent multiple >> > message >> > in one sequence with the InOrder QOS enabled. This is working, but what >> > I am >> > missing currently is that I would like the same instance of the service >> > being called for the whole sequence. I need this because the messages >> > send >> > in the sequence at the end of the sequence have to be consolidated in a >> > single response based on the content of all the messages in the >> > sequence. >> > I found that currently the messages in the sequence are processed >> > individually by seperate service instances. >> > What do you think of this? >> > >> > Thanks, >> > >> > Tijs >> > >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: [EMAIL PROTECTED] >> > For additional commands, e-mail: [EMAIL PROTECTED] >> > >> > >> >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Paul Fremantle VP/Technology, WSO2 and OASIS WS-RX TC Co-chair http://bloglines.com/blog/paulfremantle [EMAIL PROTECTED] "Oxygenating the Web Service Platform", www.wso2.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
