IT JUST WORKS :o) I am not using any SimpleSessionHandler, I just set my Call.setMantainSession( true )... and seems to work. But I am only at the beginning.
QUESTION: on client, how can I preserve the cookie after closing the call? Because for now, after calling the login remote method, I keep the same axis Call object in order to make the calls. And this should not be done like this because all the time I have to ask the call object to remove all the parameters... MUST be something wierd!!! PLS give me some advices... I have also tried to use the SimpleSessionhandler but with no success. The client is not able to get the session... in fact it does not care about a session being sent in SOAP headers!!! But I have only used .setMantainSession... A session tutorial of axis will be great (for the documentation pages) :o))) As you can see, there are alot of people asking about it... at least some faq stuff will be enough... About the MessageContext (the behaviour in client and server mode) and so on... Tx dovle > Hi, could anyone please explain how the Axis session object is accesible to > multiple web services. I experimented a lot without success. > > Thanx in advance > > -----Original Message----- > From: Grant Echols (JanusLogix) [mailto:[EMAIL PROTECTED]] > Sent: Friday, November 22, 2002 12:12 AM > To: [EMAIL PROTECTED] > Subject: Re: Session between services. > > > We've been successful at doing this using the Axis Session object to store > 'tokens' or other items that are commonly accessible by multiple published > SOAP services. > > ----- Original Message ----- > From: "Alex Dovlecel" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Thursday, November 21, 2002 6:02 AM > Subject: Session between services. > > > Hello all, > > I have started to read the "big zip" and seems pretty usefull. But before > > reading all that stuff, I want to know if I can achieve this behaviour: > > > > The web service that I am going to implement will provide many methods. > > So > > I > > > decided to split it (2, 3 or 4 web services). One of them will deal with > > login stuff and user management (get profile, change it and so on) and > > the others will provide the functionality. > > > > So I want that a user cannot connect to service2 before login (service1). > > For > > > this I decided to have a SessionObject that should be kept by the app > > server > > > and when login, adding some stuff to the session, enshuring the other > > services that this user has logged in. > > > > So can I achieve this behaviour with axis and tomcat? I am mostly > > interested > > > to do it using HttpHeaders because it should be easy for interop stuff > > (slight changes to ksoap or other clients to add the sessionId header). > > > > What do you recomend me to do? > > > > do you have some alternative design, maybe better for this situation? > > > > Where should I look first ? (the urls and javadoc classes) > > > > Tx > > dovle
