tomcat-users mailing list archives

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

>This mechanism is meant to be a standard way for web frameworks to
>the Servlet Container. IMHO this is compliant with the specification:

Your not really humble at all opinion is wrong. This is a Servlet 3.0 feature and therefore
not available to 2.5 or earlier webapps.

If you look elsewhere in the Servlet, JSP and EL specs you'll find things that would break
if the container used syntax from a newer spec version with a web app written for an older
spec. If you want to use Servlet 3.0 features then you need to declare 3.0 in the web.xml.


>"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
>container. The ServletContainerInitializer allows handling such a use
>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 <>
>> > ServletContainerInitializer
>> Only exists in Servlet 3.0. Supporting it in lower spec versions
>> be non-compliant.
>> And silly.
>> p
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
>> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message