[
https://issues.apache.org/jira/browse/OWB-481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gurkan Erdogdu closed OWB-481.
------------------------------
Resolution: Won't Fix
OWB provides default initializtion process using listener approach. Other
container can implement its own solutions.
> WebBeansConfigurationListener implementing ServletContextListener is not
> likely to work
> ---------------------------------------------------------------------------------------
>
> Key: OWB-481
> URL: https://issues.apache.org/jira/browse/OWB-481
> Project: OpenWebBeans
> Issue Type: Bug
> Reporter: David Jencks
> Assignee: Gurkan Erdogdu
>
> Currently WebBeansConfigurationListener implements ServletContextListener and
> uses the contextInitialized method to initialize OWB for the web app. Given
> an application containing a ServletContextListener that is a web bean, this
> requires that
> 1. the OWB WebBeansConfigurationListener ServletContextListener get
> installed before the app's ServletContextListeners
> 2. the OWB WebBeansConfigurationListener have it's contextInitialized called
> before the servlet container instantiates the apps ServletContextListeners
> that are web beans.
> There's no way to guarantee this will happen in a compliant servlet
> container. (Neither happens in the geronimo tomcat integration; we could
> force the first to happen, but not the second).
> It might be possible to do the initialization in a
> ServletContainerInitializer since I think these get called before any
> application classes start getting instantiated.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
