BTW: Do we need the huge batik-all.jar at all? I've seen Batik splits up into
several jars which leads me to think we only need a few of them.
Giacomo
Quoting giacomo <[EMAIL PROTECTED]>:
> On Sun, 27 May 2001, Ross Burton wrote:
>
> Hi Ross :)
>
> > 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. It would
> probably a
> > > good idea to change to this interface rather than the current
> > > implementation.
> >
> > The SAX interfaces are there because I bugged them enough. :-) When
> > they first appeared they just backed straight onto a DOM builder - but
> > that was quite a while ago. Tomorrow I'll try and get the SVG stuff
> up
> > to date with the Batik 1.0 release.
>
> That's cool, thanks.
>
> Giacomo
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
