>
> - can we make Batik act nicer? It's throwing alot of Exceptions which
> might be because it was not designed to run in a server/servlet
> environment or we use it the wrong way? Is anyone on the batik list
> or more familiar with it? Batik starts with a TranscoderException
> encloseing a null Exception and one that states "Connection reset
> by peer". Any suggestions?
Our SVGSerializer works by building a DOM document object and passing this
to Batik. This was because when the first Batik Transcoder was made
available that was the only way you could do it. Since that first release
that the SVGSerializer was based on was produced the transcoder interface
was rewritten. In that new interface came support for a
org.xml.sax.XMLReader and I believe full SAX2 support. It would probably a
good idea to change to this interface rather than the current
implementation.
People wiser than me in these matters may have a different opinion, but I
would hate for us to be using the wrong way of interfacing with batik
because we did'nt know better.
rgds
CB
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
