Dave,
While testing Batik 1.1.1 on MacOS I found I was getting the same
error as you described. After some investigation, I found that the
javaws.jar file, on Mac OS X, contains the DOM bindings. This is for
Java Web Start 1.0.1. On Win32, the bindings are not in that same
jar...
I was able to patch the javaws.jar file by hand (i.e. unjar, remove
the dom bindings, jar again). After doing that, I could launch the
demo (on http://xml.apache.org/batik/batikDemo.html) on Mac OS X.
Vincent.
> 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.
>
> JNLP is unfortunately not niggle-free at the moment. I already have to do a
> workaround with bufferedreader objects, as they always return true from
> ready() over jnlp. Im reckoning this may be a similar problem as both are
> to do with io. The problems seem to start when trying to choose a file,
> rather than doing the actual transcode.
>
> dave
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
