[
https://issues.apache.org/jira/browse/OWB-512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg resolved OWB-512.
-------------------------------
Resolution: Not A Problem
Assignee: Mark Struberg (was: Gurkan Erdogdu)
imo this is spec conform.
Where we do store the info doesn't make a difference. The important fact is
that the Context got closed and is not active anymore. This might only affect
an Extension which also accesses this context in a servlet listener. Applying a
different order in your web.xml should work - and don't ask me how to do this
with the broken servlet-3 spec ;)
> ApplicationContext and SingletonContext in WebContextsService
> -------------------------------------------------------------
>
> Key: OWB-512
> URL: https://issues.apache.org/jira/browse/OWB-512
> Project: OpenWebBeans
> Issue Type: Bug
> Components: Java EE Integration
> Affects Versions: 1.1.0
> Reporter: Gerhard Petracek
> Assignee: Mark Struberg
>
> WebContextsService shouldn't cache ApplicationContext and SingletonContext in
> thread-locals (without a fallback) because WebBeansConfigurationListener
> might call WebContextsService#endContext too early.
> if e.g. a portable extension gets invoked afterwards it can't access those
> contexts. since both contexts have to exist all the time a different approach
> (or a fallback) is needed.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
