For what it's worth, we've had both Hibernate and TopLink Essentials
available in our v1 and v2 servers with no problem. All I did was add
these (probably outdated) jars to $GF_HOME/lib:
antlr-2.7.6.jar
asm-attrs.jar
asm.jar
cglib-2.1.3.jar
commons-collections-3.1.jar
commons-logging-1.0.4.jar
concurrent-1.3.2.jar
dom4j-1.6.1.jar
ehcache-1.2.jar
ejb3-persistence.jar
hibernate-annotations.jar
hibernate-entitymanager.jar
hibernate3.jar
javassist.jar
jboss-archive-browsing.jar
log4j-1.2.11.jar
oscache-2.1.jar
And the, of course, change the persistence provider in each
persistence.xml. I guess if you want Hibernate to be default, remove
the TLE jars might work, but I've not tried that. And we've actually
just removed Hibernate altogether from our app server and are just using
TLE, for what that's worth.
-----
Jason Lee, SCJP
Senior Software Engineer
http://www.iec-okc.com
> -----Original Message-----
> From: glassfish_at_javadesktop.org [mailto:glassfish_at_javadesktop.org]
> Sent: Friday, March 23, 2007 1:40 PM
> To: users_at_glassfish.dev.java.net
> Subject: Re: Classloading Error for JPA Implementation
>
> Sorry for the confusion here.
>
> The stack trace for my first post of this thread relates to
> Hibernate JPA not being loaded. This problem is now
> temporarily solved my removing the toplink jars from the
> glassfish/lib completely.
>
> The stack trace for my second post of this thread (the same
> stack trace I posted over at hibernate forum) relates to
> Persistence.createEMF failing during webapp redeployment. I
> should have started a new thread for this error. My apology.
> [Message sent by forum member 'tmv' (tmv)]
>
> http://forums.java.net/jive/thread.jspa?messageID=209670
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>