On Sun, 27 May 2001, Colin Britton wrote:
> >
> > - 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.
Thanks for your analysis.
> It would probably a good idea to change to this interface rather
> than the current implementation.
Well, I'm not shy to ask :) a patch would be cool.
> 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.
I think we should stay with SAX where ever we can to see better
performance, smaller memory footprint etc.
Giacomo
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
