'
Subject: RE: Getting multiple instances of my servlet, although it
doesn't implement SingleThreadModel
Basically, Tomcat will create a separate instance for each unique
URL that the servlet responses to.
(Technically, every time you define the servlet in the web.xml
01, 2002 6:38 AM
To: 'Tomcat Users List'
Subject: RE: Getting multiple instances of my servlet,
although it doesn't implement SingleThreadModel
Basically, Tomcat will create a separate instance for
each unique URL that the servlet responses to.
(Technically, every time
List'
Subject: RE: Getting multiple instances of my servlet,
although it doesn't implement SingleThreadModel
I don't think this is exactly true. I have an app using the
mediator design pattern, in which there is only one servlet
handling all requests (all of my servlet mappings point
-Original Message-
From: Scott Shorter [mailto:[EMAIL PROTECTED]]
Sent: Friday, March 01, 2002 9:05 AM
To: 'Tomcat Users List'
Subject: RE: Getting multiple instances of my servlet, although it
doesn't implement SingleThreadModel
Randy,
The servlet is defined once in web.xml - one
Randy,
Thanks for clarifying what you meant.
1. Multiple servlet tags in web.xml
Nope.
2. One or more servet tag(s) in web.xml and using
/servlets/ to access your servlet
Nope.
3. Having the same context loaded multiple times.
This generally happens because the
3. Having the same context loaded multiple times.
This generally happens because the AutoContextLoader (or
whatever its called) is still enabled and an explicit Context
is also defined, making two contexts (and two instances of
the servlets).
Maybe. I do have a context
I guess I can deploy to somewhere besides webapps - that
should do it, huh?
I'll try that and let all know.
That did the trick. Thanks for the pointers, Randy and Mark.
-
Scott
--
To unsubscribe: mailto:[EMAIL PROTECTED]
For additional commands: mailto:[EMAIL PROTECTED]
Troubles with
