users@glassfish.java.net

Classloading problem when using Toplink _at_Entity

From: <glassfish_at_javadesktop.org>
Date: Wed, 02 Jan 2008 14:04:21 PST

Hi people,

I've found a thead from over a year ago on the Spring forums struggling with the very same problem. I'm using Spring 2.5 final, Glassfish v2 final and Toplink Essentials 2.0 Build b58g-fcs. Using GlassFishLoadTimeWeaver and enabling weaving in toplink then deploying via Eclipse WTP to Glassfish leads to this:

[code]
 Caused by: Exception [TOPLINK-30007] (Oracle TopLink Essentials - 2.0 (Build b58g-fcs (09/07/2007))): oracle.toplink.essentials.exceptions.PersistenceUnitLoadingException
Exception Description: An exception was thrown while loading class: com.fsdev.mvnweb.HelloEntity to check whether it implements @Entity, @Embeddable, or @MappedSuperclass.
Internal Exception: java.lang.ClassNotFoundException: com.fsdev.mvnweb.HelloEntity

...

Caused by: java.lang.ClassNotFoundException: com.fsdev.mvnweb.HelloEntity
        at com.sun.enterprise.loader.EJBClassLoader.findClassData(EJBClassLoader.java:714)
        at com.sun.enterprise.loader.EJBClassLoader$DelegatingClassLoader.findClass(EJBClassLoader.java:1376)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
        at oracle.toplink.essentials.ejb.cmp3.persistence.PersistenceUnitProcessor.isEntity(PersistenceUnitProcessor.java:316)
[/code]

Which clearly looks like a Glassfish problem to me. Packaging the exact same stuff into an EAR and deploying manually through the admin interface gets me a clear run, no problems at all.

Is that a Glassfish problem or am I wrong on this one?
[Message sent by forum member 'dyn' (dyn)]

http://forums.java.net/jive/thread.jspa?messageID=251996