geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (GERONIMO-5567) jetty servlet/filter gbeans but direct listener creation not compatible with servlet 3 startup order
Date Tue, 08 May 2012 17:47:59 GMT

     [ https://issues.apache.org/jira/browse/GERONIMO-5567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

David Jencks resolved GERONIMO-5567.
------------------------------------

    Resolution: Fixed
    
> jetty servlet/filter gbeans but direct listener creation not compatible with servlet
3 startup order
> ----------------------------------------------------------------------------------------------------
>
>                 Key: GERONIMO-5567
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-5567
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Jetty
>    Affects Versions: 3.0
>            Reporter: David Jencks
>            Assignee: David Jencks
>             Fix For: 3.0
>
>
> Programatic addition of servlets and filters needs to happen after the web.xml stuff
is processed because some operations such as servletRegistration.addServletMapping() must
do nothing if there is an existing mapping in the list.
> we could make the listeners gbeans or put all the web.xml info in the web app gbean.
 The latter would probably work for tomcat too, we'd just do the servletCOntext registration
stuff directly.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message