Same problem occurs under 4.0.4RC1, at the same place in the code. FYI, the error happens on a document.getDocumentElement() method call.
Thanks for the hint, but I've already gone through the stuff on the wiki, and it doesn't seem to apply. org.w3c.dom.Node is not part of the application, after all -- it's a system class that is normally loaded from rt.jar. In the case of JBoss 4.0.3SP1 (and probably 4.0.4 as well), it looks to me like it should be loaded from the endorsed directory, xml-apis.jar. However, I'd also think that anything in the endorsed directory would not be subject to these class-loader issues.
This particular set of beans gets loaded by a single loader bean that is the only bean that gets mentioned in the jboss-service.xml file. There's only a single deployment here, but maybe the class loader that an executing bean uses is different than the class loader that the SAR loader uses?
Any other suggestions?
Thanks for the hint, but I've already gone through the stuff on the wiki, and it doesn't seem to apply. org.w3c.dom.Node is not part of the application...
I don't believe you. Print out the code source of the Document class and the Document instance class:
If those are not different try enable trace level logging of the class loading layer.
You are correct and I am wrong -- bad .jar in the deployment. Thanks for the debugging tip, though.