xmlgraphics-batik-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vincent Hardy <vincent.ha...@sun.com>
Subject Re: Batik over JNLP
Date Mon, 17 Dec 2001 18:09:00 GMT

David Smith wrote:
> Hi Vincent,
> I thought it was probably a classpath problem too so I checked through all
> my jar files.
> Of all the jars downloaded with batik, I set all but crimson-parser.jar and
> js.jar to my
> classpath.  I am 100% sure my application cannot see the omitted jars from
> the ide.  Im not even sure I use xerces, whatever that is.
> The same jars are set in the xml part of my jnlp app.
> If it was a classpath problem, wouldn't I be getting NoClassDefFound errors?
> The DOMUtilities line it refers to contains the following:
>             if (n.hasAttributes()) {    // line 57
>                 NamedNodeMap attr = n.getAttributes();
> n is a Node object.  Looking at Node, both methods are interface
> definitions, meaning concrete classes would not compile if the methods were
> missing.
> I have checked this with both batik 1.0 and 1.1.  Both classes appear to be
> the same in both versions.

Actually, when I was saying a classpath problem, I meant that you 
probably have another version of the DOM bindings which appears in
your classpath before the ones which ship with Batik. These must be
older and not have the hasAttributes method on Node...


To unsubscribe, e-mail: batik-users-unsubscribe@xml.apache.org
For additional commands, e-mail: batik-users-help@xml.apache.org

View raw message