"Sukachevin, Stoehr" wrote:
> In looking at some of the more recent source code for v1.0, it appears that
> since the ActionServlet caches a lot of objects in the servlet context, like
> action mappings, app resources, etc., the ActionServlet was not designed to
> allow multiple instances of the servlet to be deployed in a single web
> application.
>
> In other words, if for whatever reason, one wanted to deploy multiple
> ActionServlets in a single web application so that each servlet can deal
> with its own set of action mappings, etc., this would not work with the
> current implementation of the ActionServlet.
>
> Is my understanding correct?
>
That is correct. Within the context of a single web application, the design
assumption is (and, at least as far as intent goes) always has been, that there
will be exactly one instance of the controller servlet. Separate web apps, of
course, are completely independent of each other, and will have their own custom
configured instances.
Because this question comes up occasionally, I would be interested in
understanding more about what might motivate a desire to have more than one
instance of the controller servlet. Do you have some particular use cases in
mind where this would be helpful?
>
> -- Stoehr
Craig McClanahan
