You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-dev@xmlgraphics.apache.org by Jeremias Maerki <de...@greenmail.ch> on 2005/01/14 08:48:22 UTC
Re: Xerces-dependency in Batik (was: cvs commit: xml-fop build.xml)
(cc'ing batik-dev)
If I interpret this correctly, Batik uses the following entry in
XMLResourceDescriptor.properties to instantiate a parser in
SAXDocumentFactory through the SAX XMLReaderFactory:
org.xml.sax.driver = org.apache.xerces.parsers.SAXParser
There's no Xerces-dependency in Java code, only SAX. Neither does the
PDFTranscoder use Xerces-specific functionality.
This should probably be improved in Batik.
On 13.01.2005 23:22:14 J.Pietschmann wrote:
> Jeremias Maerki wrote:
> > I see. I've added JAXP and Xerces to the classpath.
>
> Isn't it somewhat strange that org.apache.xerces.parsers.SAXParser
> is explicitely referenced? I'd think everyone uses JAXP meanwhile.
> Do you access Xerces specific functionality?
>
> J.Pietschmann
Jeremias Maerki
Re: Xerces-dependency in Batik
Posted by Thomas DeWeese <Th...@Kodak.com>.
Hi All,
Jeremias Maerki wrote:
> (cc'ing batik-dev)
>
> If I interpret this correctly, Batik uses the following entry in
> XMLResourceDescriptor.properties to instantiate a parser in
> SAXDocumentFactory through the SAX XMLReaderFactory:
>
> org.xml.sax.driver = org.apache.xerces.parsers.SAXParser
>
> There's no Xerces-dependency in Java code, only SAX. Neither does the
> PDFTranscoder use Xerces-specific functionality.
>
> This should probably be improved in Batik.
Yes, there is nothing against JAXP, this code was all written
before JAXP existed. Since then no one has taken the time to
ensure we are using it properly. Also Ideally there would be
some sort of transition where both might work.
Contributions are always welcome! ;)
> On 13.01.2005 23:22:14 J.Pietschmann wrote:
>
>>Jeremias Maerki wrote:
>>
>>>I see. I've added JAXP and Xerces to the classpath.
>>
>>Isn't it somewhat strange that org.apache.xerces.parsers.SAXParser
>>is explicitely referenced? I'd think everyone uses JAXP meanwhile.
>>Do you access Xerces specific functionality?
>>
>>J.Pietschmann
>
>
>
>
> Jeremias Maerki
>
Re: Xerces-dependency in Batik
Posted by Thomas DeWeese <Th...@Kodak.com>.
Hi All,
Jeremias Maerki wrote:
> (cc'ing batik-dev)
>
> If I interpret this correctly, Batik uses the following entry in
> XMLResourceDescriptor.properties to instantiate a parser in
> SAXDocumentFactory through the SAX XMLReaderFactory:
>
> org.xml.sax.driver = org.apache.xerces.parsers.SAXParser
>
> There's no Xerces-dependency in Java code, only SAX. Neither does the
> PDFTranscoder use Xerces-specific functionality.
>
> This should probably be improved in Batik.
Yes, there is nothing against JAXP, this code was all written
before JAXP existed. Since then no one has taken the time to
ensure we are using it properly. Also Ideally there would be
some sort of transition where both might work.
Contributions are always welcome! ;)
> On 13.01.2005 23:22:14 J.Pietschmann wrote:
>
>>Jeremias Maerki wrote:
>>
>>>I see. I've added JAXP and Xerces to the classpath.
>>
>>Isn't it somewhat strange that org.apache.xerces.parsers.SAXParser
>>is explicitely referenced? I'd think everyone uses JAXP meanwhile.
>>Do you access Xerces specific functionality?
>>
>>J.Pietschmann
>
>
>
>
> Jeremias Maerki
>
---------------------------------------------------------------------
To unsubscribe, e-mail: batik-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: batik-dev-help@xml.apache.org