geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ivan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (GERONIMO-5634) Improve ServletContainerInitializer support
Date Thu, 07 Oct 2010 01:07:31 GMT

    [ https://issues.apache.org/jira/browse/GERONIMO-5634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12918752#action_12918752
] 

Ivan commented on GERONIMO-5634:
--------------------------------

Not sure what you mean that the current implementation did not support searching for classes
with an annotation when the annotation is specified in the "interested in" annotation ? I
remembered that I added a new finder in the xbean to take it ?


> Improve ServletContainerInitializer support
> -------------------------------------------
>
>                 Key: GERONIMO-5634
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-5634
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: javaee6, Jetty, Tomcat, web
>    Affects Versions: 3.0
>            Reporter: David Jencks
>
> Our ServletContainerInitializer is incomplete and not osgi friendly.  We currently don't
support searching for classes with an annotation when the annotation is specified in the "interested
in" annotation. Also we look for ServletContainerInitializers at deploy time not run time.
 Although I used to think this was OK, I no longer think it is sufficiently osgi friendly.
 I think we need to look for both ServletContainerInitializers when starting the web app using
ServiceLocator (as well as in the bundle itself) and look for the classes in the bundle and
any fragment bundle that may have been added since deployment.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message