I'm really not aware of any non-http level session stuff going on right now.
It wouldn't be hard to write a set of interceptors that would do this for JMS. The server "in" interceptor would just pull a session ID from someplace (soap header or JMS header or similar) and validate it and store it on the exchange/message to be used later in the implementation or similar. An "out" interceptor would add it to the response. Client side would be similar. Dan On Fri February 6 2009 3:53:49 am anoopPrasad wrote: > Dear All, > > I have Integrated the latest CXF 2.1.3 with my system and it started > working without making much noise (Some noise near the JMS area ;-) ;change > in the way we were configuring it) > > We do have a need to maintain session for certain Web Services for > licensing the same for certain Service consumers.I started exploring > options within CXF and found an interesting discussion here > http://www.nabble.com/session-management-td11326045.html > But that discussion focused on HTTP/jetty based session handling. > > Do we have a mechanism to handle the Sessions at the application layer > level itself; something like what they have in Axis2. If yes kindly point > me in the right direction. > If not please let me know if we have any work in progress in this > direction. > > Thanks in advance. > > regards > anoopPrasad -- Daniel Kulp [email protected] http://www.dankulp.com/blog
