>>> Gokul Singh <[EMAIL PROTECTED]> 07-Sep-00 2:58:13 PM >>>
>I was wondering that the Specs are silent on this type of
>facility being provided by the containers. So are the servlet
>containers *required* to provide this facility or is it an optional
>facility which they may provide.
It's optional. Always has been... but so many people use it (or used
to) that it is kinda required by default.
Even in these days of web.xmls and WAR files it's still kinda usefull
to drop a class somewhere and have the servlet engine serve it
automatically.
I'm getting quite affectionate about it now actually /8-)
>Is this type of facility really required today(2.2 and onwards) or
>is it just a frill provided by the servlet containers reminiscent of
>the old days.
I'm still supporting code that uses this antique loading mechanism
and I probably will be for a while. /8-<
I'd like to be able to support that code with the latest servlet
containers.
>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.
One *could* create mappings for the /servlet autoloading in other
contexts thus allowing the antiquated loading mechanism with other
more, modern tricks like context paths and context init params.
Nic
___________________________________________________________________________
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
