>>>>> "VI" == Vinny Iyer <[EMAIL PROTECTED]> writes:
VI> I read that it might be caused by a conflict between w3c.jar and
VI> batik.jar but I never had the w3c.jar.
The conflict is with an incomplete implementation of DOM level 2
(I think, this is really out of my area).
VI> Also, I have only the batik.jar in my classpath (which works fine
VI> for the batch file), do I need other batik jars like batik-ext.jar
VI> etc. ? Here is a list of all the jars I have included in the
VI> project. Maybe one of them is causing the conflict.
I'm really not a 'DOM guy' but I think xerces may have to come
after the Batik stuff on the classpath... Basically I would put Batik
first, Fop second, and the rest of the stuff later :)
Also be aware that stuff in the jre/lib/ext dir is also
'on your classpath' and can cause problems. I would check all the
jars for classes in the w3c package:
In UNIX:
% jar -tvf XXX.jar | grep org.w3c
VI> servlet.jar fop.jar xml.jar xalan-2.0.0.jar jimi-1.0.jar cos.jar
VI> xerces-1.2.3.jar jdom.jar xalanj1compat.jar batik.jar
VI> Thanks again for your help and patience.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
