Well 1 yr, 7 months later...
...perhaps you are no longer developing, this issue having driven you to move into management
I have a non-answer answer.
I've hit this issue upon upgrade to Spring 2.5.5 in a Spring-Hibernate web app running in
JBoss 4.0.3SP1. I was on 2.0.1 (or thereabouts) and things worked. Based on one of the (now) 4 Google hits on this, I focused on classloading in JBoss. My web app ships with the hibernate jars and worked fine prior to the Spring upgrade. Come to find that JBoss 4.0.3SP1 also ships and loads hibernate jars (jboss-home/server/default/lib). Seems somehow now suddenly there's a conflict, or the JBoss version of the hib jars is taking precedence and it's version doesn't work with the new Spring. When I remove the hibernate jars from the server install, things work.
That's ok, but I want my app's version of the jar to be used, and my impression is that as of JBoss 4.0.2 it should be being used. I'd rather not have to remove or change the JBoss config if I can help it.
btw, here's the somewhat helpful Google hit, which was probably helpful for other versions of JBoss (pre 4.0.2?):
https://jira.jboss.org/jira/browse/JBAS-1691
Any thoughts appreciated.
Any thoughts? Anyone?