Wes, Though this list isn't intended for servlet discussion...I'm fairly certain that there is (by default) exactly one instance of a servlet produced by an application server (unless you go the SingleThreadModel route). I think the servlet specification will back me up on this one: http://www.jcp.org/aboutJava/communityprocess/final/jsr053/ (see srv.2.2).
Thanks for the clarification on MessageContext... Cory -----Original Message----- From: Wes Devauld [mailto:[EMAIL PROTECTED]] Sent: Friday, January 24, 2003 9:38 AM To: [EMAIL PROTECTED] Subject: Re: Axis MessageContext Firstly I don't think there is only one instance of a servlet for all calls to a web context. The reason all member variables are static is because it does create several servlets. With Servlets you do have to deal with mulitple threading issues. Second, MessageContext.getCurrentContext does correspond to the current request. Just what I've found, I may be wrong. -Wes > Two questions: > 1) Like servlets, is there exactly one instance of the service I've > exposed via axis? 2) If so, can I operate under the assumption that > MessageContext.getCurrentContext() directly correlates to the current > request? Much like Thread.currentThread()? Thanks! > Cory
