[ https://issues.apache.org/jira/browse/OWB-931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13894906#comment-13894906 ]
Romain Manni-Bucau commented on OWB-931: ---------------------------------------- I see, in EE using TCCL shouldn't break that much things so I propose to do the fix then check if TomEE is still passing TCKs on 1.2 branch. If so let's go this way. > NormalScopeProxyFactory classloader usage > ----------------------------------------- > > Key: OWB-931 > URL: https://issues.apache.org/jira/browse/OWB-931 > Project: OpenWebBeans > Issue Type: Brainstorming > Components: Core > Affects Versions: 1.2.0 > Reporter: Moritz Bechler > Labels: ClassLoader, OSGI > > 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? -- This message was sent by Atlassian JIRA (v6.1.5#6160)