Hi Andy,
Usually class cast exceptions with JBoss indicate that you have several
jars of the same library in your class path. The class looks proper but
being loaded with different class loaders, it's actually different.
So what you should do now is to carefully check the JBoss class path to
see where do the org.apache.xerces.jaxp.DocumentBuilderFactoryImpl and
javax.xml.parsers.DocumentBuilderFactory come from.
I believe there's a tool (somewhere in JBoss console) that lets you see
where the classes in the classpath were loaded from.
Regarding your question about slf4j - most likely you did the right thing
:)
http://xwiki.475771.n2.nabble.com/Proposal-Switch-from-Commons-Logging-Log4…
Regards,
Roman
--
View this message in context:
http://xwiki.475771.n2.nabble.com/XWiki-war-JBoss-AS6-MySQL-tp6309076p63566…
Sent from the XWiki- Users mailing list archive at
Nabble.com.