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.
>I invite you to take a look at the mail archive for futher details.
I tried to search the mail archive for "JAXP or TrAX", both batik-users and
batik-dev, but I found nothing. Does the search function work properly?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
