[jira] Reopened: (OWB-369) Static ContextsService in ContextFactory causes wrong webContextService used for multiple applications

["Mark Struberg (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/OWB-369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Struberg reopened OWB-369:
-------------------------------

      Assignee: Mark Struberg  (was: YING WANG)

Due to this change, the cost of getting the ContextsService each time is pretty high.
I will further improve this by maintaining a Map to cache the ContextsService depending on the ClassLoader which is being used.

> 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.