[
https://issues.apache.org/jira/browse/OWB-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg reopened OWB-1055:
--------------------------------
After reviewing the spec again and testing with a few tomcat and jetty versions
it turned out that all the destroy events are fired in the reverse order than
the init events. This is actually exactly as we need it.
I think we should remove the Begin and End listeners again and move back to a
single WebBeansConfigurationListener.
> Split WebBeansConfigurationListener in Begin and End listeners
> --------------------------------------------------------------
>
> Key: OWB-1055
> URL: https://issues.apache.org/jira/browse/OWB-1055
> Project: OpenWebBeans
> Issue Type: Improvement
> Components: Context and Scopes
> Affects Versions: 1.5.0
> Reporter: Mark Struberg
> Assignee: Mark Struberg
> Priority: Minor
> Fix For: 1.6.0
>
>
> Currently we only have a single WebBeansConfigurationListener. The CDI
> Listener should be the outermost in the chain. The problem is that the order
> in which the Listeners get called is per Servlet Spec (a clarification foo)
> is the same for every event. There is no difference between all the init* and
> destroy* events.
> So if you have multiple Listeners in your app then we can only guarantee that
> the CDI Listeners init* methods get called first but _not_ the destroy
> methods.
> For that to work we need to split those methods in a
> BeginWebBeansConfigurationListener and EndWebBeansConfigurationListener.
> The current WebBeansConfigurationListener should simply delegate to those 2
> for backward compatibility.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
