Nic Ferrier wrote:
> >>> Gokul Singh <[EMAIL PROTECTED]> 07-Sep-00 2:58:13 PM >>>
>
>
> >If the container does provide this facility, then by what I
> >understand, it translates into the fact that servlet container
> >has an in built ServletContext mapped to '/servlet'.
>
> No. It's usually provided as part of the default servlet context.
>
> In Tomcat I suspect it's defined in the ROOT WAR file.
>
For Tomcat 3.1 in particular, this is configured in the
$TOMCAT_HOME/conf/web.xml file, which configures all of the "default"
facilities for each web app. You will note a servlet definition for the
"invoker" servlet, and a servlet mapping that maps "/servlet/*" to this
servlet. You could, for example, change the mapping to "/servlets/*" and
emulate what some popular servlet containers like Apache JServ do (although you
will also need to tweak your Apache configuration if you are using
Apache+Tomcat). Or, you can disable this facility by removing this servlet
definition and mapping.
That is how Tomcat happens to do this -- every servlet container configures it
their own way.
>
> Nic
>
Craig McClanahan
====================
See you at ApacheCon Europe <http://www.apachecon.com>!
Session VS01 (23-Oct 13h00-17h00): Sun Technical Briefing
Session T06 (24-Oct 14h00-15h00): Migrating Apache JServ
Applications to Tomcat
___________________________________________________________________________
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
