[
https://issues.apache.org/jira/browse/OWB-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12865043#action_12865043
]
Gurkan Erdogdu commented on OWB-369:
------------------------------------
OpenWebBeans libraries must not be on the global class loaders (global class
path), it has not written to work like this. Only spi and api modules could be
on the global class path of the container.
> 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.
