The only place I could see this working in the "all" configuration would be
inside a webapp where the 2.0 jars were included in WEB-INF/lib. In all other deployment
types, a parent-first classloader is used, which would pick up the 1.x version of JBC in
server/all/lib.
If you're neither using HttpSession replication nor clustered EJB3 EJBs nor JBC as a
Hibernate 2nd level cache, then you could probably remove the relevant services and
upgrade the JBC version in server/all/lib. There may be other incompatibilites though;
e.g. incompatible versions of JBoss AOP,
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4002545#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...