> > I'm seeing a behaviour that suggests instantiation of servlets
> > due to an invocation via a "servlet-mapping" or via the
> > InvokerServlet (/servlet) are handled differently.
> >
> > More specifically, given that I've set up a Context for
> > the path "/foo", and within that context, I've mapped
> > "/some" to SomeServlet.
> >
> > If I make a request to http://localhost/foo/some, I can
> > see the creation of an instantiation of SomeServlet.
> > But, if I also make the request to
> > http://localhost/foo/servlet/SomeServlet, I see an additional
> > creation of an instance of SomeServlet.
> >
> > Is this an intentional behaviour or a bug?
...snip...
> The concept of an "invoker" servlet (i.e. the "/servlet/*" handler) is
> not in the servlet specification at all (which only considers <servlet>
> to be a servlet definition), but is commonly implemented in servlet
> containers. What happens is, the first time you invoke a servlet via
> /servlet/xxxxx, a new servlet definition is created dynamically. The
> dynamically created servlet definition will have its own ServletConfig
> structure with no servlet initialization parameters.
Oooohh. This belongs in the "List of Things You Should Know"
