[ 
https://issues.apache.org/jira/browse/JUDDI-401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tom Cunningham resolved JUDDI-401.
----------------------------------

    Resolution: Fixed

Documented in the devguide.

> Need to document that 3.0.2 now uses openjpa enhanced classes by default 
> (Caused by: java.lang.ClassNotFoundException: No ClassLoaders found for: 
> org.apache.juddi.model.Address)
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JUDDI-401
>                 URL: https://issues.apache.org/jira/browse/JUDDI-401
>             Project: jUDDI
>          Issue Type: Bug
>    Affects Versions: 3.0.2
>            Reporter: Tom Cunningham
>            Assignee: Tom Cunningham
>             Fix For: 3.0.3
>
>
> If I try substuting the 3.0.2 juddi-core JAR into my hibernate app I see the 
> following :
> Caused by: java.lang.ClassNotFoundException: No ClassLoaders found for: 
> org.apache.juddi.model.Address
>         at org.jboss.mx.loading.LoadMgr3.beginLoadTask(LoadMgr3.java:212)
>         at 
> org.jboss.mx.loading.RepositoryClassLoader.loadClassImpl(RepositoryClassLoader.java:521)
>         at 
> org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassLoader.java:415)
>         at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
>         at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:316)
>         at java.lang.Class.forName0(Native Method)
>         at java.lang.Class.forName(Class.java:247)
>         at 
> org.hibernate.util.ReflectHelper.classForName(ReflectHelper.java:112)
>         at 
> org.hibernate.ejb.Ejb3Configuration.classForName(Ejb3Configuration.java:1005)
>         at 
> org.hibernate.ejb.Ejb3Configuration.addNamedAnnotatedClasses(Ejb3Configuration.java:1077)
> It seems like hibernate will not pick up the openjpa enhanced classes - if I 
> build the 3.0.2 tag with hibernate and then sub that JAR in, this exception 
> disappears.      We should document this.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to