Changing Hibernate Version in JBoss SOA 5.0.2?

[andypickler]

In my WAR application I would like to use a different version of Hibernate (hibernate-core 3.6.8-Final and other compatible Hibernate packages) than the one provided by my server: JBoss SOA 5.0.2, which ships with Hibernate Core 3.3.2.  I have followed the advice/instructions in every web page I could find.  Here are all my current configurations:

jboss-classloading.xml:

<classloading xmlns="urn:jboss:classloading:1.0"  

              name="ggp-ws.war"  

              domain="ggp-ws"> 

              parent-domain="Ignored" 

              top-level-classloader="true"

              export-all="NON_EMPTY"  

              import-all="true"

              parent-first="false">  

</classloading>

jboss-web.xml:

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE jboss-web PUBLIC "-//JBoss//DTD Web Application 5.0//EN"

    "http://www.jboss.org/j2ee/dtd/jboss-web_5_0.dtd">

<jboss-web>

    <class-loading java2ClassLoadingCompliance="false">

        <loader-repository>

            com.aircell:loader=ggp-ws.war

            <loader-repository-config>java2ParentDelegation=false</loader-repository-config>

        </loader-repository>

    </class-loading>

    <context-root>/ggp-ws</context-root>

</jboss-web>

Added entry in server/default/deployers/metadata-deployer-jboss-beans.xml:

<entry>

               <key>persistence_2_0.xsd</key>

               <value>org.jboss.metadata.jpa.spec.PersistenceMetaData</value>

            </entry>

Tried many different configurations of entry in server/default/deployers/jbossweb.deployer/META-INF/war-deployers-jboss-beans.xml:

   <bean name="WarClassLoaderDeployer" class="org.jboss.web.tomcat.service.deployers.WarClassLoaderDeployer">

      <property name="relativeOrder">-1</property>

      <property name="filteredPackages">javax.servlet,org.apache.commons.logging</property>     

   </bean>

Tried adding packages, child packages, commenting out the whole thing, etc.

Yet still from all I can tell it seems that JBoss is using the version of Hibernate in common/lib rather than what I have packaged with my WAR.  Any final advice?  And no...the organization is not willing to upgrade to a newer JBoss version at this time nor consider an app server that doesn't have these classloader issues.