tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Violeta Georgieva <>
Subject Re: Using ServletContainerInitializer for 2.5 applications
Date Thu, 12 Apr 2012 11:33:10 GMT

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

is that not only we be able to plug-in things that are bundled in the

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

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.


2012/4/12 Pid * <>

> On 11 Apr 2012, at 14:42, Lazar Kirchev <> 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:
> For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message