"jaikiran" wrote : | So i guess its the responsibility of JBoss XB to switch the classloader. | By the way, switching the classloader is only going to fix the classcastexception. Switching the classloader would mean that the xerces class will end up being used from what is shipped in JBoss (or for that matter in any other application server). So it really needs to be a question asked in the xerces-J forums whether there is any practical way to overriding the xercesImpl jars in a application server environment where multiple classloaders are involved.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4249890#4249890 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4249890 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
