[
https://issues.apache.org/jira/browse/OWB-369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
YING WANG updated OWB-369:
--------------------------
Attachment: ContextFactory.patch
Thanks Gurkan, Joe. With Gurkan's recent changes, my second app still fails.
How are we going to handle static ContextService in ContextFactory? I have
uploaded this patch to replace it with local variables in the class. It might
not be optimized, but requires minimum code changes. Please help review. Thanks
in advance.
> 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: YING WANG
> Fix For: 1.0.0
>
> 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.
