> DOMException "(The current node (type: 2, name: contentStyleType) is > read-only)", which probably happens much earlier !? I couldn't imagine > that this parse error happens because of the x server issue. Any > comments?
As I said, I have no experience with the 1.3 JVM, but looked into the apidocs for 1.3.1 and a difference with the 1.4 that caught my attention was the absence (in 1.3) of the package 'org.w3c.dom', which is exactly the package where the stated exception occurs. ( For 1.3 this is not a core package ) I also read on the batik pages that batik can be compiled without DOM ( for smaller distros ). Compare the size of batik binary distribution to the size of the batik jar that came with fop... ( the fop lib-dir also contains the xml-apis.jar, which contains org.w3c.dom, amongst others ) I guess we have found which library is missing or inaccessible. ( I'm inclined to believe that this has sth to do with the fact that you used the batik jar included with fop to run batik standalone... true? Don't know if it works, or if it is supposed to. Do you get the same error when using the batik distribution? ) Cheerz, Andreas Delmelle --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
