All, Subsequent client requests to my service don't appear to be retaining state. I'm certain that I'm missing something rather trivial here re: session management but I can't find any documentation regarding the matter. That said, I have found the following tid bit: "It is up to some handler on the request chain to set up an appropriate Session implementation and attach it to the MessageContext with MessageContext.setSession() so that anyone who wants to use session semantics can get at it." I see the lovely AxisHttpSession object that can be constructed from an HttpServletRequest or HttpSession -- but I'm unsure of how to get to either/both through a handler OR a service. Any input is warmly welcomed. Thanks! Cory
- Re: Session management Alex Dovlecel
- Re: Session management Alex Dovlecel
- RE: Session management Mike Oliver
- Re: Session management Pae Choi
- RE: Session management Johnson, Tim
- Re: Session management Alex Dovlecel
- Re: Session management Alex Dovlecel
- RE: Session management Mike Oliver
- Re: Session management michel
- RE: Session management Cynthia M Kimball
- Re: Session Management Cory Wilkerson
- Re: Session Management bin
- RE: Session Management Josh Kropf
- Re: Session Management Barry Levinson
- RE: Session Management Chakraborty, Anirban
- RE: Session Management Cory Wilkerson
- RE: Session Management Mike Burati
- Session Management Saradhi Vemuri
- Re: Session Management Toshiyuki Kimura
- Re: Session Management Sateesh Ayyagari
- session management Pathuru, Kiran