|
This is a class loader problem. The class loader
used to load dom4j doesn't seem capable of finding saxpath which is part of the
dom4j-full.jar. Could you try adding dom4j-full.jar to your system classpath
instead.
I'm not really sure what JavaWebServer2.0 is or how
its class loading works. Certainly dom4j 1.0 seems to work fine in Servlet 2.2
& Servlet 2.3 standard servlet engines, like tomcat 4.0, when using
web-applications and putting dom4j-full.jar in the WEB-INF/lib. If ever you have
a doubt about some thorny servlet-based classloader issue, one workaround is add
your jar to the system classpath.
James
|
