Gary,
Perhaps Xalan could to do a couple of things:
1) Load the parser
2) Check if it is Xerces, and Xerces of the right version (or version
range)
If it is not Xerces or Xerces with the right version it could use vanilla
interfaces.
Just a though,
Bran Minchau
"Gary L Peskin"
<[EMAIL PROTECTED]
om> To
<[EMAIL PROTECTED]>
02/13/2004 12:36 cc
AM
Subject
RE: Question on parser pluggability
Please respond to and using different xerces versions
xalan-dev
This is an excellent question. I haven't looked at the code in some time.
However, it used to be that Xerces was special cased and, if the parser was
Xerces, some internal APIs were used to facilitate incremental processing.
Those internal APIs were subject to change from release-to-release and so
the caveat was documented.
For non-Xerces parsers, those internal APIs were, obviously, not available,
and Xalan uses vanilla JAXP interfaces.
HTH,
Gary
> -----Original Message-----
> From: Vishwajit Pantvaidya [mailto:[EMAIL PROTECTED]
> Sent: Thursday, February 12, 2004 2:48 PM
> To: [EMAIL PROTECTED]
> Subject: Question on parser pluggability and using different
> xerces versions
>
>
> Hello,
>
> A question about xalan java (I am using xalan java 2.0.0).
> The release notes
> say the following: "The Xalan-Java version 2.0.0 has been tested with
> Xerces-Java version 1.2.3. The Xalan-Java version 2.0.0 download from
> xml.apache.org includes xerces.jar from Xerces-Java version
> 1.2.3....Important You may experience unpredictable anomalies
> if your Xalan
> and Xerces builds are not in synch. If you download an update
> to Xalan,
> check the release notes to determine which version of Xerces
> you should
> use.". So it appears that it is not recommended to use a
> xerces version
> other than 1.2.3 with xalan 2.0.0.
>
> At the same time, the doc talks about pluggability of other
> parsers in the
> section "Plugging in a Transformer and XML parser".
>
> My question is: If I can plugin other parsers, why is it a
> problem to plugin
> a different xerces version? Also, if xalan internally uses standard
> interfaces (like JAXP) to call the parser, I would presume that any
> conformant parser would work.
>
>
> Please help in understanding this apparent anomaly.
>
>
> Thanks,
>
> Vishwajit.
>
> _________________________________________________________________
> Plan your next US getaway to one of the super destinations here.
> http://special.msn.com/local/hotdestinations.armx
>
