[
https://issues.apache.org/jira/browse/OWB-605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13092340#comment-13092340
]
Gerhard Petracek commented on OWB-605:
--------------------------------------
it's the other way round. e.g. mojarra bootstraps everything very early and
that's pretty often a problem.
first of all the "underlying" container has to be started (in this case cdi)
and then impls which might use it already during bootstrapping.however, outside
of app-servers there is currently no deterministic way to define which impl
comes first if std. configs get used because other libs could use the same
mechanism.
> tomcat plugins must not always register WebBeansConfigurationListener as
> first Listener
> ----------------------------------------------------------------------------------------
>
> Key: OWB-605
> URL: https://issues.apache.org/jira/browse/OWB-605
> Project: OpenWebBeans
> Issue Type: Bug
> Components: Java EE Integration
> Affects Versions: 1.1.0
> Reporter: Mark Struberg
> Assignee: Mark Struberg
> Fix For: 1.1.1
>
>
> Currently the ContextLifecycleListener of our tomcat6 and tomcat7 plugins
> always register all OWB specific servlet listeners as first in the list.
> This is problematic in conjunction with JSF because certain CDI Extensions
> rely on JSF being started already.
> We should introduce a way to specify listeners which must be registered
> before our own OWB specific Servlet listeners.
> This could be in the form of an openwebbeans.properties
> /**
> * comma separated list of servlet listeners which OWB must not be registered
> before (if they exist).
> */
> openwebbeans.contextlifecyclelistener.after=org.apache.myfaces.web.StartupServletContextListener,com.sun.mojarra....
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
