https://issues.apache.org/bugzilla/show_bug.cgi?id=45616
Jeremias Maerki [EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
https://issues.apache.org/bugzilla/show_bug.cgi?id=45727
Jeremias Maerki [EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
https://issues.apache.org/bugzilla/show_bug.cgi?id=45734
Jeremias Maerki [EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
No. At runtime, FOP doesn't care what XSLT processor is used as long as
it's JAXP compatible. Inside the test code there's a hard reference to
Xalan for XPath processing. But that's unrelated to XSLT in general. The
runtime code doesn't have a dependency on Xalan.
On 05.09.2008 13:53:16 Philip V
One could potentially have a code path using the latest JAXP XPath
facilities to avoid requiring Saxon...
Of course XPath is a bit funny. Saxon's XPath does not return live
nodes from the original DOM you hand to it. Xalan's does -- but ever
since 2.1.0 has assumed that you're going to do a
