You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openwebbeans.apache.org by "Gurkan Erdogdu (JIRA)" <ji...@apache.org> on 2010/07/03 10:44:50 UTC
[jira] Closed: (OWB-369) Static ContextsService in ContextFactory
causes wrong webContextService used for multiple applications
[ https://issues.apache.org/jira/browse/OWB-369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gurkan Erdogdu closed OWB-369.
------------------------------
Resolution: Fixed
> Static ContextsService in ContextFactory causes wrong webContextService used for multiple applications
> ------------------------------------------------------------------------------------------------------
>
> Key: OWB-369
> URL: https://issues.apache.org/jira/browse/OWB-369
> Project: OpenWebBeans
> Issue Type: Bug
> Affects Versions: M4
> Reporter: YING WANG
> Assignee: Mark Struberg
> Fix For: 1.0.0-CR1
>
> Attachments: ContextFactory.patch
>
>
> To reproduce,
> Application A, which does not support conversation, installed and tested without any issue. then stop and uninstalled.
> Application B, which support conversation, get installed and started.
> When test Application B, ApplicationA's contextService is used and causes conversation scope is not found since it does not support conversation.
> The problem is because of static variable used for contextsService in ContextFactory which is JVM-wide and only init once. While supportConversation flag is application-wide property.
> Probably we need contextService variable to be classloader based instead of static variable. or need some change to supportsConversation flag.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.