-
1. Re: Why Hibernate 3.2.4.sp1?
pmuir Oct 30, 2007 10:28 AM (in response to nagypalg)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?
nagypalg Oct 30, 2007 10:41 AM (in response to nagypalg)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 Oct 30, 2007 10:44 AM (in response to nagypalg)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 Oct 30, 2007 10:44 AM (in response to nagypalg)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?
nagypalg Oct 30, 2007 12:10 PM (in response to nagypalg)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.