Re: Batik transcoding API and JAXP

[Thierry Kormann <tk...@ilog.fr>]

On Friday 29 June 2001 20:37, Mikael Ståldal wrote:
> At 14:19 2001-06-29 +0200, Thierry Kormann wrote:
> >Using JAXP in Batik can be done outside the scope of any Batik modules.
> > There are several reasons discussed later on this mailing list explaining
> > why we decided to not use JAXP.
> >
> >Basically, we have a way to set an XML parser for all batik modules
> > (Canvas, Transcoder, ...). The XML parser classname is specified in a
> > property file and can be easily changed.
>
> My question was not how Batik find the XML parser to use, it was why one
> can not use the TrAX API (JAXP 1.1 transformation API) to access the Batik
> transcoding function. However, I also wonder why Batik doesn't use JAXP to
> find an XML parser.

We didn't want to use jaxp because we don't need it. Users can easily use 
jaxp if they want to specify the XML parser to use in batik.

TrAX is mainly designed for XSLT engines. The transcoder module does not 
transform SVG to XML but provide a generic API to transform SVG to raster 
images for example.

Thierry.

 


---------------------------------------------------------------------
To unsubscribe, e-mail: batik-users-unsubscribe@xml.apache.org
For additional commands, e-mail: batik-users-help@xml.apache.org