In case of session scope, each session has its own instance of the service class independently of which thread invokes the exposed methods. I suppose that the servlet engine starts a new thread for each request, at least MessageContext.getCurrentContext() works in such manner. In case of application scope, for example, each request is handled by the same class instance. Take a look at org\apache\axis\providers\java\JavaProvider.java. Regards.
> -----Original Message----- > From: Rajal Shah [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, September 18, 2002 1:18 AM > To: [EMAIL PROTECTED] > Subject: Session scope and threaded request? > > > Hello. > > When the scope of the service is "session", then do each > request come as a separate thread and invokes the appropriate > method in the class (like the servlet behaviour?) > > If not, do I need to extend my service class to a predefined > Axis class get this behavior? > > Any blurb on how the requests are processed in such scenarios > (session scope and application scope) will be much appreciated. > > Regards. > -- > Rajal >
