[OWB-931] NormalScopeProxyFactory classloader usage

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.2.0
• Fix Version/s: 1.5.0
• Component/s: Core
• Labels: ClassLoader OSGI
• Assignee: Mark Struberg
• Reporter: Moritz Bechler
• Created: 07/Feb/14 16:14
• Updated: 19/Apr/15 14:53
• Resolved: 12/Apr/15 18:48

Description

createNormalScopeProxy currently uses the bean class ClassLoader for two purposes:
1. defining the proxy class
2. instantiation of the instance provider.

In our OSGI/WAB environment this usage does not make much sense:
1. the proxy class should be defined in the classloader which most closely reflects the CDI context lifecycle, which is the web context TCCL.
2. causes trouble with scope providers (e.g OWB's own RequestScopedBeanInterceptorHandler) when they are defined in another bundle. I don't think there is a proper compatible solution to this (except maybe making extensions fragments) but also trying the TCCL makes this much more painless to use.

Is there any explanation for this particular choice of classloaders? Are there any reasons not to try TCCL first?

Issue Links

• relates to: OWB-972 Define an Application Boundary SPI