[OWB-369] Static ContextsService in ContextFactory causes wrong webContextService used for multiple applications

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: M4
• Fix Version/s: 1.0.0-alpha-1
• Assignee: Mark Struberg
• Reporter: Ying Wang
• Created: 07/May/10 03:03
• Updated: 03/Jul/10 08:43
• Resolved: 03/Jul/10 08:43

Description

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.