This doesn't seem to be a problem with dom4j but with your JAXP configuration. It's not very clear what could be wrong. But it seems to be missing a vital ingredient ... could it be that you don't have the xmlParserAPIs.jar included in your classpath?
What JDK/JRE are you using? Regards, Edwin ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ dom4j-user mailing list dom4j-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dom4j-user
