At 09:27 2001-09-13 +0200, Thierry Kormann wrote:
> > Why isn't JAXP used to find the parser to use?
>
>Batik is an SVG toolkit and the XML parser is really the low level part of
>our SVG implementation. In Batik, there is a class (XMLResourceDescriptor)
>that easily lets you control how to get the XML parser for *all* batik
>modules - so users can easily control how the XML parser is created (using
>JAXP or not).
Yes, but why isn't JAXP used to find the parser to use, if the user doesn't
explicitly specify one?
>We have decided to provide a low level solution on purpose. We don't see the
>need of using JAXP in our low level approach - but users can do it if they
>want to (how and which XML parser is better for their system).
The point of using JAXP is that the user doesn't have to invoke some method
in the Batik API, she only have to install her favorite JAXP compatible
parser in the CLASSPATH (perhaps Xerces).
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
