You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openwebbeans.apache.org by "Gerhard Petracek (JIRA)" <ji...@apache.org> on 2013/02/21 22:46:13 UTC
[jira] [Updated] (OWB-784) WebContextsService bypasses spi contract
of ContextsService
[ https://issues.apache.org/jira/browse/OWB-784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gerhard Petracek updated OWB-784:
---------------------------------
Description:
WebBeansConfigurationFilter, WebBeansConfigurationListener and WebContainerLifecycle are bound to WebContextsService (due to #removeThreadLocals).
-> #removeThreadLocals should be part of the ContextsService spi (e.g. #resetThreadBoundData)
or we introduce a new interface e.g. ThreadAware and #resetBoundData only gets called if a custom ContextsService implements it.
was:
WebBeansConfigurationFilter, WebBeansConfigurationListener and WebContainerLifecycle are bound to WebContextsService (due to #removeThreadLocals).
-> #removeThreadLocals should be part of the ContextsService spi (e.g. #resetThreadBoundData)
> WebContextsService bypasses spi contract of ContextsService
> -----------------------------------------------------------
>
> Key: OWB-784
> URL: https://issues.apache.org/jira/browse/OWB-784
> Project: OpenWebBeans
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.1.7
> Reporter: Gerhard Petracek
> Fix For: 1.2.0
>
>
> WebBeansConfigurationFilter, WebBeansConfigurationListener and WebContainerLifecycle are bound to WebContextsService (due to #removeThreadLocals).
> -> #removeThreadLocals should be part of the ContextsService spi (e.g. #resetThreadBoundData)
> or we introduce a new interface e.g. ThreadAware and #resetBoundData only gets called if a custom ContextsService implements it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira