Ales Justin wrote:
Hmmm, how can this happen if both you and JBossAS use the same Hibernate version?
That's confusing to me, too. When I build my war using the default "compile" scope I have these jars inside WEB-INF/lib:
hibernate-commons-annotations-3.2.0.Final.jar
hibernate-core-3.6.0.Final.jar
hibernate-entitymanager-3.6.0.Final.jar
hibernate-jpa-2.0-api-1.0.0.Final.jar
hibernate-commons-annotations-3.2.0.Final.jar
hibernate-core-3.6.0.Final.jar
hibernate-entitymanager-3.6.0.Final.jar
hibernate-jpa-2.0-api-1.0.0.Final.jar
I've verified that those jars are not in my war when I build using the "provided" scope.
These versions seem to be the same as in the JBoss distribution. The only one that's different is hibernate-commons-annotations, which is "6.0.0.Final" in the manifest. (It would be nice if the libs in $JBOSS_HOME/common/lib would have the version numbers as part of the filename, so I didn't have to go into each one and look at the manifest to determine what versions they are!)
I did find this kind of interesting:
$ ls -l /appserver/jboss-6.0.0.Final/common/lib/hibernate-core.jar
-rw-rw-r--@ 1 chriscouncil staff 3116797 Dec 28 08:30 /wdev/jboss-6.0.0.Final/common/lib/hibernate-core.jar
$ ls -l /m2repo/org/hibernate/hibernate-core/3.6.0.Final/hibernate-core-3.6.0.Final.jar
-rw-r--r-- 1 chriscouncil staff 3083100 Oct 14 16:22 /mm/org/hibernate/hibernate-core/3.6.0.Final/hibernate-core-3.6.0.Final.jar
My hibernate jars come from the jboss public repo at https://repository.jboss.org/nexus/content/repositories/public, so I'd expect them to be the same size. Obviously the MD5 sums don't match ;) I haven't checked any further, though.