5 Replies Latest reply on Oct 30, 2007 12:10 PM by nagypalg

    Why Hibernate 3.2.4.sp1?

      Is there any particular reason to bundle Hibernate 3.2.4.sp1 with Seam 2 instead of the newest Hibernate 3.2.5.ga version? If there is no reason, would not it be a good idea to update this dependency in the official distribution?

      Citation from root-2.0.0.CR3.pom at http://repository.jboss.org/maven2:

      <dependency>
       <groupId>org.hibernate</groupId>
       <artifactId>hibernate</artifactId>
       <version>3.2.4.sp1</version>
      ...
      

      --
      Gabor

        • 1. Re: Why Hibernate 3.2.4.sp1?
          pmuir

          We try where possible to keep in track with JBoss AS 4.2. 4.2.2.GA is using Hibernate 3.2.4.sp1.

          • 2. Re: Why Hibernate 3.2.4.sp1?

            OK, this is a valid reason. So I will use the newest Hibernate version with Seam 2 unofficially. ;)

            • 3. Re: Why Hibernate 3.2.4.sp1?
              pmuir

              Of course, I see no reason why that won't work (we have had to move to newer versions of some hibernate stuff like annotations and entitymanager to get compatibility with hibernate search, so its not a solid rule). But, really, it matters what version of hibernate you *deploy* not compile against as the hibernate api is pretty stable.

              • 4. Re: Why Hibernate 3.2.4.sp1?
                pmuir

                Which of course, if you use JBoss AS is 3.2.4.sp1 unless you upgrade it.

                • 5. Re: Why Hibernate 3.2.4.sp1?

                  No, I do not use JBoss AS, so it is not a problem. And Hibernate 3.2.5.ga has a new Oracle10gDialect that I would like to use. Anyway, Seam works nice with Hibernate 3.2.5.ga for me, I just wanted to make sure that there are no known issues with it.