Dwayne Schultz wrote:
Can you confirm that Batik should be able to take a Xerces DOM document and that creating a SVGDOMDocument is unnecessary?
Should yes, I don't know that I personally have used a Xerces DOM. If you can provide a sample app I can run it and see exactly what is happening (or you can get the Batik Source dist and do the same for yourself).
The ideal thing would be to take the existing test case for converting a 'generic' dom (which still uses the Batik DOM) to the SVG DOM and modify it slightly to use a Xerces parser/DOM. Then if you choose to contribute it our regression testing would ensure that we don't break this code path in the future.
The existing test is: xml-batik/test-sources/org/apache/batik/transcoder/image/GenericDocumentTest.java
The document is valid SVG because if I dump it out as text and pass it to the batik command line tool it gets converted to PNG just fine. Whether I pass it as an XSL result or allow Xerces to parse it off the disk (in both cases it is a Xerces DOM document) I get the same error in Batik. Here is the whole document:
So the Xerces parse of disk is interesting, but still looking at the code that is generating the error it seems like Xerces is returning something 'odd' - we may need to work around that oddity but what ever.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
