[
https://issues.apache.org/jira/browse/EXTCDI-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12885885#action_12885885
]
Mark Struberg commented on EXTCDI-28:
-------------------------------------
sounds reasonable. I'll retest with geronimo3 again after I fixed the
geronimo-openwebeans-plugin.
My previous attempt was by packaging the owb jars inside my EAR. I need to test
how this behaves with owb being provided directly by the container.
Generally:
When does CodiFacesContextWrapper get called, and is OWB alraedy up and running
at this time?
The faces-config.xml gets scanned at MyFaces startup when the FacesServlet gets
started in web.xml.
OWB typically gets started as via a
ServletContextListener#contextInitialized(). Since they are defined to fire
this method _before_ any servlet gets started all should work fine in theory.
I'll dig deeper into geronimo3 and tomcat7 to see what's going on.
> CodiFacesContextWrapper in some scenarios throws a NPE because
> BeanManagerProvider hasn't yet been initialized
> --------------------------------------------------------------------------------------------------------------
>
> Key: EXTCDI-28
> URL: https://issues.apache.org/jira/browse/EXTCDI-28
> Project: MyFaces CODI
> Issue Type: Bug
> Components: JEE-JSF12-Module
> Affects Versions: 1.0.0-SNAPSHOT
> Reporter: Mark Struberg
>
> It seems that in some situations the CodiFacesContextWrapper constructor
> get's called before the BeanManagerProvider got initialized. In this case the
> constructor fails with a NullPointerException while getting the BeanManager.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
