[
https://issues.apache.org/jira/browse/OWB-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12865159#action_12865159
]
Gurkan Erdogdu commented on OWB-369:
------------------------------------
Joe,
As I said OWB not written for tiered-class loaders. So all of the loaded
classes must be loaded by each web application classloaders therefore does not
collide with each other.
For example: Each web application has its own webbeans-finder class and
different ConversationManager.
> 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
>
>
> 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.
