[OWB-512] ApplicationContext and SingletonContext in WebContextsService

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Not A Problem
• Affects Version/s: 1.1.0
• Fix Version/s: 1.1.1
• Component/s: Java EE Integration
• Assignee: Mark Struberg
• Reporter: Gerhard Petracek
• Created: 03/Jan/11 18:58
• Updated: 30/Aug/11 09:27
• Resolved: 21/Mar/11 15:26

Description

WebContextsService shouldn't cache ApplicationContext and SingletonContext in thread-locals (without a fallback) because WebBeansConfigurationListener might call WebContextsService#endContext too early.
if e.g. a portable extension gets invoked afterwards it can't access those contexts. since both contexts have to exist all the time a different approach (or a fallback) is needed.