I have had the problem of servlets that are loaded on startup being loaded
again (init method firing again) on their first access by a client. This
issue has been discussed a lot on the list over the last year and I have not
seen a solution that would work for me.
I have found that if you set the <servlet-name> entry equal to the
<servlet-class> entry in the web app's web.xml file that it will solve the
problem.
Evidently, Tomcat is determining what servlets are loaded by checking the
servlet-name entries and not the servlet-class entries. I think this should
be considered a bug.
Craig Smithpeters
Senior Software Engineer
Nielsen Media Research
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
