Hmmm, that works I guess, but for some reason it seems like there should be a standard way of doing this. If I can start a session I would like to be able to end it. But, to summarize, these are the two ways to end a session in Axis2 1.2 (secretly hoping an Axis developer/expert will say "no, you just use the _____ method that already exists, dummy"):
1) Disable sessions (I think that means operate in request scope ?) and then write your own session handling as described by Robert (pass in a session id with each request) or 2) Just let the session expire when it happens to time out (and probably add an endSession action to your service so that you can wipe your session data)... On 7/4/07, robert lazarski <[EMAIL PROTECTED]> wrote:
I've always thought that web service sessions - in any framework - don't play nice together or even in the same framework. In the axis2 case, I've seen a lot of confusion in this area and after reading countless emails and several articles about it, and reading the code, I still don't entirely get how it would handle what I typically need. This isn't a criticism - I'm just saying I think sessions need to be tailored to each specific case beyond the basics. Therefore I tend to roll my own and just generate the session key - I like to use java 5 and UUID - and manage it myself on the server side, forcing the client to manually pass it back in on every request after login. It took me a mere two days to write the code and I've used it in several projects since. Not very standard, but as I said, the standard ways never really worked for me. It might be worth exploring rolling your own as its not too difficult. HTH, Robert On 7/4/07, fat suze <[EMAIL PROTECTED]> wrote: > > Does anyone know if there is any documentation anywhere on the web that > explains axis2 sessions? Specifically the ending of sessions? I have > searched all over the web for how to kill a transport session, and I have > seen many others asking how to end all types of sessions, but nobody seems > to know.... :) Is it impossible? > Thanx > Susanne > > > > On 7/4/07, Stadelmann Josef <[EMAIL PROTECTED] > wrote: > > > > Hi developers ... :-) > > > > Running multipple clients, each talkes to an instance of > > MyService5.java ; > > > > MyService5.java has init(), login(), map(), logout(), destroy(), > > implemented; > > > > It was said somewhere in this mailing-list that init() and destroy() > > methods get called at the proper time by axis2 if they are implemented; this > > hhrough reflection. > > > > My simple question is: > > > > How do I properly terminate such a session from my Client code > > (avoiding problems to axis2) when > > a) MyService5 runs in scope=soapsession and > > b) has a long timeout set to 86'400'000 milliseconds (= > > 24hr's)? > > c) init() and destroy() are ONLY to be called by axis2 itself > > > > > > Josef Stadelmann > > @axa-winterthur.ch > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > >
