> -----Original Message-----
> From: Clay Leeds [mailto:[EMAIL PROTECTED]
> Could you explain how one would 'plug in Saxon 7 instead' of Xalan for
> parsing?
Maestro,
Should be quite simple really: replace the Xalan jar in your JVM's
'lib/endorsed' directory with Saxon's jar. (Maybe to make sure all goes
well, you could also replace it in FOP's own lib directory, then rebuild
FOP, but IIRC this shouldn't be necessary...)
Try it, and use the following in your XSLT to check:
<xsl:value-of select="system-property('xsl:vendor')" />
The theory:
FOP never references classes in Xalan's own packages (org.apache.xalan.*).
All Xalan does for us is offer an implementation for the
javax.xml.transform.* API spec. Any provider of an implementation for these
packages --Saxon, for example-- should work seamlessly with FOP.
The javax.xml.transform API spec hasn't been altered in any way as a result
of XSLT/XPath 2.0 --it didn't *need* to be, which is the whole point, of
course... XSLT can continue to evolve, but the javax.xml.transform API
should be generic enough to support possible changes.
In the same fashion, one could opt to use an XML parser other than Xerces.
We offer Xerces and Xalan because we can distribute them freely with FOP.
(We could also have opted not to distribute *any* XML parser or XSLT engine,
and leave it all up to the end-user, but this would needlessly complicate
things --no more running FOP 'out-of-the-box' :-( )
Cheers,
Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
