Hmm. Why doesn't hibernate.rar or hibernate use the Thread's context classloader?
You can resolve the MBean name conflict by changing the <display-name>
and <adapter-display-name> for one deployment.
JBoss4 has a better way to avoid this confict.
Your sidenote should be the HTTPD forum.
Please stick to one question <-> one thread so that others can find/follow the solutions.
But look in jbossweb-xxx.sar/META-INF/jboss-service.xml
It was a user bug... :)
Hibernate does use the Thread's classloader first, except when loading it's properties. So copying the properties to the conf dir solved the issue.
But thanks for the info, it's helped to understand things better!
I owe you a beer, now you only need to visit Hungary once! :)