On Sun, Jan 3, 2010 at 1:52 AM, Bruno Simioni <brunosimi...@gmail.com>wrote:
> Please, could you give me an example, to solve this problem using > WS-Addressing ? > > My problem is about acess the same service using different clients. One > client consumes the service using Javascritp, and the another one, the Java > Service Client. > > Although the Javascript client gets the related message Id, how can I use > this on Java Clent? > so your problem is to share a one session among different clients? I think there is no standard way to do this. even with the http sessions you need to copy the cookie which contains the JSESSION to other requests. thanks, Amila. > > Regards, > > Bruno. > > On Sat, Jan 2, 2010 at 9:53 AM, Yashvant chauhan <c.yashv...@gmail.com>wrote: > >> Use WS-Addressing for stateful web service.. >> >> >> >> On Sat, Jan 2, 2010 at 3:46 PM, Bruno Simioni <brunosimi...@gmail.com>wrote: >> >>> Amila, thats about JAX-WS services. >>> >>> Here's the situation: >>> >>> First Access >>> ------- HTTP Session 1------- >>> Client1 (JavaScript) -> Axis2 -> JAX-WS Service1 >>> ------- HTTP Session 1------- >>> >>> Second Access >>> ------- HTTP Session 1------- >>> ------- HTTP Session 2------- >>> Client1 (Java, Service Client, WSA) -> Axis2 -> JAX-WS Service2 >>> ------- HTTP Session 2------- >>> ------- HTTP Session 1------- >>> >>> On First Acess, there is one HTTP Session created by my web container >>> (Tomcat), and it is used for authentication purposes (application logic). >>> >>> On Second Acess, because of WSA, there is two HTTP Sessions! >>> >>> How to solve this? >>> >>> Bruno. >>> >>> >>> >>> >>> n Sat, Jan 2, 2010 at 12:10 AM, Amila Suriarachchi < >>> amilasuriarach...@gmail.com> wrote: >>> >>>> in which scope you have deploy your service? >>>> >>>> please have a look at here[1]. >>>> >>>> thanks, >>>> Amila. >>>> >>>> [1] http://wso2.org/library/articles/stateful-web-services-axis2 >>>> >>>> >>>> On Fri, Jan 1, 2010 at 7:05 PM, Bruno Simioni >>>> <brunosimi...@gmail.com>wrote: >>>> >>>>> Needing some help with HTTP sessions. >>>>> >>>>> When sending a SOAP simple message to Axis2, it create a single HTTP >>>>> session to handle the client message, and to handle the client HTTP POST >>>>> request. >>>>> >>>>> When sending a WSA SOAP message (by Axis2 Java Client), it creates >>>>> another http session to handle the WSA soap header, and then process the >>>>> message. The first one HTTP session persist, but inside any module or >>>>> webservice, I have only acess to the second one. That´s a problem to me, >>>>> since I need the first one session, for authorization purposes >>>>> (application >>>>> logic) >>>>> >>>>> How to remove this second http session? I need only ONE http session, >>>>> for all SOAP messages that I send. >>>>> >>>>> ps. Client setManageSession(true) does not solve the problem. >>>>> >>>>> Regards, >>>>> >>>>> Bruno. >>>>> >>>> >>>> >>>> >>>> -- >>>> Amila Suriarachchi >>>> WSO2 Inc. >>>> blog: http://amilachinthaka.blogspot.com/ >>>> >>> >>> >> >> >> -- >> ******************************************** >> Yashvant Singh Chauhan >> Mobile- 09845277271 >> Bangalore >> >> ********************************************* >> > > -- Amila Suriarachchi WSO2 Inc. blog: http://amilachinthaka.blogspot.com/
