RE: Servlet Deployment Problem

[Bodycombe, Andrew]

http://jakarta.apache.org/tomcat/faq/misc.html#invoker

-Original Message-
From: Miles, Fiske III [NTWK SVCS] [mailto:[EMAIL PROTECTED] 
Sent: 28 October 2003 20:10
To: [EMAIL PROTECTED]
Subject: Servlet Deployment Problem


I've spent 6-8 hours trying to figure out why Tomcat (ver 4.1.27) could not
find servlet classes using a standard
http://localhost:8080/%CATALINA_HOME%/appdir/servlet/ServletName url.

While trying to run this down I used a stack of JSP development manuals, the
WROX Apache Tomcat manual, and the Jakarta website to no avail. I tried
every conceivable permutation of deployment web.xml file, server.xml file
and app directory structure (carefully following directions from multiple
books).

The solution was finally found in a devshed forum -- the invoker servlet
mapping has been commented out of the conf/web.xml file in the binary
distribution.

Why

My second question is where would documentation for this issue reasonably be
found?

Fiske
(frustrated JSP developer)

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Servlet Deployment Problem

[Shapira, Yoav]

Howdy,

I've spent 6-8 hours trying to figure out why Tomcat (ver 4.1.27) could
not
find servlet classes using a standard
http://localhost:8080/%CATALINA_HOME%/appdir/servlet/ServletName url.

Your first mistake is assuming the above URL is a standard.  It's not,
and the servlet specification does not mandate that a servlet container
support such URLs.

The solution was finally found in a devshed forum -- the invoker
servlet
mapping has been commented out of the conf/web.xml file in the binary
distribution.

Why

The invoker servlet was disabled for security reasons.  This is in the
release notes for every tomcat version since 4.1.18.  It's also in the
tomcat FAQ (http://jakarta.apache.org/tomcat/faq), and has been
discussed many times on this list (so searching the list archives would
have revealed this information).  Many books, as is nearly always the
case for this field, are out of date.

Yoav Shapira



This e-mail, including any attachments, is a confidential business communication, and 
may contain information that is confidential, proprietary and/or privileged.  This 
e-mail is intended only for the individual(s) to whom it is addressed, and may not be 
saved, copied, printed, disclosed or used by anyone else.  If you are not the(an) 
intended recipient, please immediately delete this e-mail from your computer system 
and notify the sender.  Thank you.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]