Where's JBoss 5 loading these jars from

[vybe3142]

When deploying an ear file that contains an updated version of the hibernate3.jar (version 3.6), I noticed that I was getting some errors that pointed to the fact that an older version of hibernate was being used. Turning up the hibernate debug level, I see the following when starting up JBOSS:

16:07:24,811  INFO Version:154 - Hibernate Annotations 3.4.0.GA

16:07:24,842  INFO Environment:146 - Hibernate 3.3.1.GA

16:07:24,858  INFO Environment:146 - hibernate.properties not found

16:07:24,858  INFO Environment:146 - Bytecode provider name : javassist

16:07:24,874  INFO Environment:146 - using JDK 1.4 java.sql.Timestamp handling

16:07:24,967  INFO Version:154 - Hibernate Commons Annotations 3.1.0.GA

16:07:25,014 DEBUG HibernateSearchEventListenerRegister:104 - Search not present in classpath, ignoring event listener registration.

Any ideas on how to figure out how how / why Hibernate 3.3.1.GA is being invoked. I've checked and double checked that the latest hibernate jar is packaged within my application ear file.

Thanks,

Vin

[peterj]

JBoss AS ships with Hibernate - it uses it for JPA. The JARs are in common/lib.

[vybe3142]

Thanks.

Specifically, the hibernate core jar has a manifest thus:

Manifest-Version: 1.0

Implementation-Title: Hibernate Core

Implementation-Version: 3.3.1.GA

Built-By: steve

Specification-Vendor: Hibernate.org

Created-By: Apache Maven

Implementation-URL: http://hibernate.org/hibernate-core

Implementation-Vendor: Hibernate.org

Implementation-Vendor-Id: org.hibernate

Build-Jdk: 1.5.0_15

Specification-Title: Hibernate Core

Specification-Version: 3.3.1.GA

Archiver-Version: Plexus Archiver

Part 2 of my question. How can I modify the JBoss AS class loader behaviour for my app in order to use the HIbernate 3.6 jars that we've packaged in the ear, .. or is there a better option..

I saw some posts earlier this morning regarding modifying the jboss-app.xml but that was for earlier JBoss versions.