Maybe I should re-phrase my question to be more specific...

If we have an instance of our servlet instantiate another class (to do
testing-related stuff) that's not registered by Tomcat, do we have to worry
about threading issues among these other classes?

In other words, servlet X instantiates class Y that's not registered with
the servlet container. If multiple Xs instantiate multiple Ys, is there a
chance that the class-level (instance) variables in Y1 and Y2 can get
corrupted by each other's data?

As I understand it, this could potentially happen when dealing with
servlets, but what about classes instantiated by a servlet but not
registered with the servlet container?

Thanks.
___________________________________
Ray Bivens



-----Original Message-----
From: Christopher K. St. John [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 21, 2002 11:23 AM
To: [EMAIL PROTECTED]
Subject: Re: Single thread model in Tomcat


"Bivens, Raymond E." wrote:
>
> Since the tests can be quite lengthy anyway, my logic is
> to use a single threaded model
>


 I'm not following your logic. How does the fact that the
tests are lengthy imply you have to use SingleThreadModel?


--
Christopher St. John [EMAIL PROTECTED]
DistribuTopia http://www.distributopia.com

___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".

Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html

___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".

Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html

Reply via email to