Hi, This mechanism is meant to be a standard way for web frameworks to extend the Servlet Container. IMHO this is compliant with the specification:
"8.2.4 Shared libraries / runtimes pluggability In addition to supporting fragments and use of annotations one of the requirements is that not only we be able to plug-in things that are bundled in the WEB-INF/lib but also plugin shared copies of frameworks - including being able to plug-in to the web container things like JAX-WS, JAX-RS and JSF that build on top of the web container. The ServletContainerInitializer allows handling such a use case as described below." Lazar just wants to extend the Servlet Container using this standard mechanism. He wants his implementation of ServletContainerInitializer to be invoked for every web application. Regards Violeta 2012/4/12 Pid * <p...@pidster.com> > On 11 Apr 2012, at 14:42, Lazar Kirchev <lazar.kirc...@gmail.com> wrote: > > > ServletContainerInitializer > > Only exists in Servlet 3.0. Supporting it in lower spec versions would > be non-compliant. > > And silly. > > > p > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
