Your Application includes the org.w3c.dom interfaces in a jar file, thus jboss will load the class from there. The problem is that the DomElement itself is created by the jboss classloader not the RAR Application ClassLoader. Now it tries to assign the dom element of type Element (loaded by jbossClassLoader) to an dom element type Element (loaded by ApplicationClassLoader) which is not the same class (2 different class loaders). BANG.
Solution for the moment (as the jboss guys do not seem to fix it) remove the org.w3c interfaces from your ear file and you will automatically use the ones supplied with jboss. then it works View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3912253#3912253 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3912253 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
