John Swapceinski wrote:

> Thank you very much, Craig, for your detailed answer to my question.
> With your help I've now gotten the SnoopServlet to show its
> initialization parameters.  It is interesting that the init parameters
> are displayed when I use the URL:
> http://localhost:8080/snoop
>
> but they are NOT displayed when I use the URL:
> http://localhost:8080/servlet/SnoopServlet
> (which is what I had been doing)
>
> Is this the expected behavior?  Is it possible to load the init
> parameters when using the second URL by making some change to the
> servlet.properties file (or any other file)?
> Thanks again,
>
> John

Yes, that is expected behavior.  Initialization parameters are tied to a
"named" servlet, whereas you are telling the servlet engine to load an
anonymous servlet class -- that is, one that is not described in the
configuration parameters.

I have not tried this, but see what happens with:
    http://localhost:8080/servlet/snoop
(in other words, use the alias instead of the class name).  However,
because it is so easy to map a URI prefix, or a filename extension, to a
servlet in the mappings.properties file, I cannot see much need for this
even if it works.

The gadget that responds to the "/servlet" URI and loads anonymous
servlets is often called the "invoker" in servlet engine circles.  Some
environments might consider the ability to do this a security risk, so
the JSDK servlet engine lets you turn it off by setting "invoker=false"
in the webapp.properties file for the servlet context you are running in.

Craig

___________________________________________________________________________
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

Reply via email to