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 < [email protected]> 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 <[email protected]>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/ >
