aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Ross (JIRA)" <>
Subject [jira] [Commented] (ARIES-1019) JPA weaving hook must be called before proxy weaving hook.
Date Wed, 27 Feb 2013 17:25:12 GMT


John Ross commented on ARIES-1019:

I also opened for openjpa's consideration.
> JPA weaving hook must be called before proxy weaving hook.
> ----------------------------------------------------------
>                 Key: ARIES-1019
>                 URL:
>             Project: Aries
>          Issue Type: Bug
>          Components: JPA, Proxy
>            Reporter: John Ross
> Caused by: <openjpa-2.2.2-SNAPSHOT-r422266:1446295 nonfatal general error> org.apache.openjpa.util.GeneralException:
An error occurred while enhancing itemjpa.ItemJPA. Exception message: java.lang.ClassNotFoundException:
>     at
>     at org.apache.openjpa.enhance.PCClassFileTransformer.transform0(
>     at org.apache.openjpa.enhance.PCClassFileTransformer.transform(
>     at org.apache.openjpa.persistence.PersistenceProviderImpl$ClassTransformerImpl.transform(
>     at org.apache.aries.jpa.container.weaving.impl.WrappingTransformer.transform(
>     at org.apache.aries.jpa.container.weaving.impl.JPAWeavingHook.weave(
>     ... 48 more
> Caused by: java.lang.IllegalArgumentException: java.lang.ClassNotFoundException: org.apache.aries.proxy.weaving.WovenProxy
>     at serp.util.Strings.toClass(
>     at serp.util.Strings.toClass(
>     at serp.bytecode.BCClass.getDeclaredInterfaceTypes(
>     at
>     ... 53 more 
> This issue occurs when the Apache Aries Proxy weaving hook gets called before the Apache
Aries JPA weaving hook. Proxy weaves the class with the WovenProxy interface and adds the
necessary dynamic package imports. JPA then gets called and uses PCEnhancer which, in turn,
calls BCClass.getDeclaredInterfaceTypes, which ultimately calls Class.forName using the woven
interface's name. The class loader is from the bundle whose class is being woven. Per the
OSGi spec, dynamic imports do not take effect until after the entire weaving process is complete.
Consequently, the bundle's class loader does not yet have visibility to the class.
> One solution would be to ensure that the jpa weaving hook is always called before the
proxy weaving hook using the service ranking property.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message