On Thu, 24 Oct 2002, jdst wrote:
> hi, bob.
>
> I found the reason of the problem .
> in my classpath I use a dom4j.jar, and when dom4j.jar is in front of
> jaxen-full.jar(or jaxen-core.jar etc), the problem will appear, otherwise,
> no problem.
dom4j embeds jaxen. You don't need to use jaxen directly if you're
uding dom4j.
If you have both dom4j.jar and jaxen.jar in your path, then you effectively
have 2 jars of Jaxen. And classloading rules says that might cause
breakage.
-bob
-------------------------------------------------------
This sf.net email is sponsored by: Influence the future
of Java(TM) technology. Join the Java Community
Process(SM) (JCP(SM)) program now.
http://ad.doubleclick.net/clk;4729346;7592162;s?http://www.sun.com/javavote
_______________________________________________
Jaxen-interest mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jaxen-interest
