Hi Ronak,
Did you have any success installing 3.6? I'm about to try the same thing and
am not sure if its worth the effort.
Regards,
Dan
Ronak Patel wrote:
>
> Hi,
>
> Yes that's an add-on you install via the Update Center. The reason I put
> Hibernate into the shared classloader is specifically because I have
> multiple
> war files all using Hibernate and don't want Hibernate to be loaded into
> memory
> more than once. I'm not sure if the OSGI model of Glassfish prevents that
> even
> if you put Hibernate into the Web Application Classloaders.
>
> That being said; using the Update Center approach has been pretty reliable
> for
> me...since Sun/Oracle already did the hard work in making sure everything
> plays
> nicely.
>
> I will have to try installing Hibernate 3.6.0 on my own into there and see
> what
> happens I guess...no other way around it...
>
> Ronak
>
>
>
> ________________________________
> From: "glassfish_at_javadesktop.org" <glassfish_at_javadesktop.org>
> To: users_at_glassfish.dev.java.net
> Sent: Wed, October 27, 2010 3:09:57 AM
> Subject: Re: Hibernate 3.6.0
>
> Hi Ronak,
>
> I don't know about the "Hibernate JPA Provider" you mentioned - is that an
> add-on you installed via the Update Center?
>
> Anyway, I used to work with several 3.5.x versions of Hibernate on
> Glassfish,
> and I simply let Maven include Hibernate and all dependent libraries in my
> WAR
> file.
>
>
> Using Hibernate on Glassfish 3.0.1, you may run into the following
> problems:
>
> 1) Your app may cause memory leaks on redeployment due conflicting usage
> of the
> javasisst bytecode provider used both by Weld (CDI) and Hibernate. See
> https://glassfish.dev.java.net/issues/show_bug.cgi?id=12368
>
> Using cglib as bytecode provider for Hibernate by adding the following
> line to
> your domain.xml may solve the problem:
>
> <jvm-options>-Dhibernate.bytecode.provider=cglib</jvm-options>
>
> 2) Using some of the newest JPA 2.0 features, I ran into a number of bugs
> and
> omissions in Hibernate 3.5.x. These issues are still marked as unresolved
> in
> Hibernate JIRA.
>
> Eclipselink also has problems in this area, and OpenJPA 2.0.1 is currently
> the
> only JPA provider that works for me smoothly.
>
> Of course, you may be perfectly happy with Hibernate or Eclipselink if you
> don't
> use any of these features.
>
> Best regards,
> Harald
> [Message sent by forum member 'hwellmann']
>
> http://forums.java.net/jive/thread.jspa?messageID=486326
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>
>
>
--
View this message in context: http://old.nabble.com/Hibernate-3.6.0-tp30058812p30259480.html
Sent from the java.net - glassfish users mailing list archive at Nabble.com.