Hi,
That is how SOAP is supposed to run; a request scope just means that a new
instance of the service implementation is used to handle each request, it
does not mean that the new instance gets created in a new JVM.
If you have variables that you want refreshed on a per instance basis, I
would suggest that you use instance variables instead of static variables.
Nirmal.
Uzay Takaoglu
<uTakaoglu@simp To: "'[EMAIL PROTECTED]'"
lexis.com> <[EMAIL PROTECTED]>
cc:
07/17/2001 Subject: Service scope defiened as
Request but still
01:21 PM static vars are not r einitialized on
Tomcat 3.2.2 (not
Please respond a different JVM!!)
to soap-user
Hi All,
I have been running my soap 2.2 Java service on Linux, Tomcat 3.2.2. The
service contains classes with some static variables defined. To
reinitialize
the static variables per request basis I defined the service scope as
"Request". However, it seems like the static vars are not reinitialized
meaning multiple SOAP requests run under the same JVM and after the request
is completed the JVM is not killed.
Any ideas would be very appreciated,
Regards,
> > > >
Uzay Takaoglu
Sr. Software Engineer
Simplexis
> > eCommerce for the Business of Education
www.simplexis.com
640 2nd Street
San Francisco, CA 94107
Direct: 415.354.2061
Cell: 415.845.7831
Fax: 415.354.2099
