Thank you Charles It appears that a combination of <servlet>element(s) and <servlet-mapping>(s) elements does the trick.
I can now hit the servlet using my servlet-mapping url entry. No matter what, I cannot call the servlet by using the com.xxx.xxx.ServletName. But that was sloppy anyway, and it looks much better calling the url-entry. Thanks, Scott -----Original Message----- From: Caldarale, Charles R [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 28, 2006 10:26 AM To: Tomcat Users List Subject: RE: Tomcat 5.5 Possible Context Question > From: Scott Purcell [mailto:[EMAIL PROTECTED] > Subject: Tomcat 5.5 Possible Context Question > > Is a context entry required somewhere > in order to fire up servlets? No, it's only required when you need some Tomcat-specific attributes for the webapp, such as <Resource> definitions. Were you using the dreaded invoker servlet in 4.x? This is now disabled, since it creates significant security risks. In lieu of the invoker servlet, you should be providing servlet mappings in the web.xml of each app. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
