[ 
https://issues.apache.org/jira/browse/OWB-931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13900487#comment-13900487
 ] 

Moritz Bechler commented on OWB-931:
------------------------------------

Unfortunately build of tomEE 1.6.0/trunk is broken against current owb_1.2.x:

[INFO] -------------------------------------------------------------
[ERROR] COMPILATION ERROR : 
[INFO] -------------------------------------------------------------
[ERROR] 
tomee-trunk/container/openejb-core/src/main/java/org/apache/openejb/cdi/CdiEjbBean.java:[302,150]
 cannot find symbol
  symbol:   method getCompleteInjectionTarget()
  location: class 
org.apache.webbeans.portable.events.generics.GProcessInjectionTarget
[ERROR] 
tomee-trunk/container/openejb-core/src/main/java/org/apache/openejb/cdi/OpenEJBLifecycle.java:[197,27]
 cannot find symbol
  symbol:   method defineBeanInterceptorStack()
  location: variable cdiEjbBean of type org.apache.openejb.cdi.CdiEjbBean


> 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
>         Attachments: OWB-931-v1.patch, OWB-931-v2.patch
>
>
> 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)

Reply via email to