I am not sure what you mean... It depends what you mean by 'session'. By default there is no concept of a session. Like I said, the message context is actually piggy-backed with the soap message as soon as it is received by axis. As the soap message passes through axis, and is then passed to an invokation of your service, the same context is still 'attached' to it. You can then make the method call I described earlier to gain access to the message context. So in each invokation of your service you have access to the message context associated with a particular request message.
Like I said, this is all explained in the Axis user guide and architecture guide so you should really read those. I appologise if I have misunderstood your problem but if I have then please explain your problem in more detail. Jim > -----Original Message----- > From: Hans Jakob Skovenborg [mailto:[EMAIL PROTECTED] > Sent: 18 August 2003 15:08 > To: '[EMAIL PROTECTED]' > Subject: SV: Axis MessageContext to the WebService > > > Hej Jim > How does that work with concurrent WebServices? Wont you get a > MessageContext belongs to another session. > /Jakob > > -----Oprindelig meddelelse----- > Fra: Jim Harris [mailto:[EMAIL PROTECTED] > Sendt: 18. august 2003 15:10 > Til: [EMAIL PROTECTED] > Emne: RE: Axis MessageContext to the WebService > > > Jakob > > Usually the MessageContext is available to a Web service invoked by axis > through the static method of the MessageContext class as follows: > > MessageContext msgContext = MessageContext.getCurrentContext(); > > I think that is the one... > > HTH > Jim > > > -----Original Message----- > > From: Jakob Skovenborg [mailto:[EMAIL PROTECTED] > > Sent: 16 August 2003 08:06 > > To: [EMAIL PROTECTED] > > Subject: Axis MessageContext to the WebService > > > > > > How do I pass the Axis MessageContext from the Pivot Handler to the > > WebService. My Webservice has to get access to a backend service which > > need the UserID from MessageContext. /Jakob > > > >
