On Friday 15 October 2010 3:10:24 pm Daniel Kulp wrote: > On Friday 15 October 2010 8:24:58 am Benson Margulies wrote: > > If I needed some concept of sessions persisting across multiple calls, > > what would I do? > > Well, you can get the HTTPServletRequest from the context (there is a > standard JAX-WS property for that) and use the session directly. You can > grab the current message from PhaseInterceptorChain.getCurrentMessage and > grab the exchange and the session from that. Etc.....
One note about this that probably should be mentioned: right now, only the HTTP transports support any type of session. Thus, technically, using the HTTPServletRequest is fine. HOWEVER, the Session was stuck on the Exchange LONG LONG ago and wrappered with our own API specifically so that at some point, we could implement the various WS-* specs that do sessiony things. Just never really had a need/demand to add that though. Thus, the sessions won't work with JMS and the other transports. However, an interceptor could easily create a new Session backed by something and stick that on the exchange for use with this. -- Daniel Kulp [email protected] http://dankulp.com/blog
