Unfortunately (as far as I can tell) there is no propagation of the current MessageContext into a service when you're using a provider such as RPCProvider. I hacked my version of the RPCProvider to stuff the message context into a ThreadLocal variable before invoking the method in the Java code, but I'm sure there should be a better approach. The code can then read the message context out of the thread local.
When I finally understand Axis handler-chains, I'm sure I will be able to have one which does this for me, so I don't have to hack the providers. Simon. ----- Original Message ----- From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, May 22, 2002 12:11 PM Subject: Re: Access to HttpSession > > Take a look at the MessageContext class in Axis. You can use the > following: > > MessageContext.getCurrentContext().getSession() > > This will return an Axis "Session" object. > > You can use this to indirectly get/set attributes stored in the > HttpSession. > > > -Mark > > > -------------------------------------------------- > There is no spoon. > -------------------------------------------------- > > > > Craig Servin > <cservin@ebenx To: [EMAIL PROTECTED] > .com> cc: > Subject: Access to HttpSession > 05/22/2002 > 02:46 PM > Please respond > to axis-user > > > > > > > Is there a way to get at the session data from a SOAP service written in > Axis? > > Right now we do all of our authentication via some Filters that once you > are > authenticated put some objects to allow app level security queries into the > > HttpSession. It would be nice if we could reuse that same structure for > SOAP > services to find out what their capabilities are. > > Thanks for any suggestions, > > Craig > > > > >
