On 27/02/14 21:47, Christopher Schultz wrote:
Has anyone ever manually-plugged an EXSLT function into Xalan?
No, I changed the processor to Saxon so I can use XSLT2. The date and
time functions there are much better and more extensive, and there is no
need for plugins.
///Peter
--
Peter
Hi Chris,
Not standard EXSLT functions, but I have loaded extension functions under 2.1.
I’ve just consulted my archives (2006!)…
Firstly, I used a .xweb patch file patch Cocoon’s servlet configuration, in
order to pre-load my extension classes using Cocoon's load-class init-param;
this was
Hi,
We have used EXSLT in C2 stylesheets without problems.
Here is an excerpt:
xsl:stylesheet xmlns:xsl=http://www.w3.org/1999/XSL/Transform;
version=1.0 xmlns:exslt=http://exslt.org/common;
...
xsl:if test=exslt:node-set($content)/checkboxes/checkbox[not(@selected)]
...
As far as memory
Chris, one more notice. Take a look at:
http://saxonica.com/documentation9.4-demo/html/extensions/exslt.html
EXSLT are available out of the box in Saxon 9.x EE/PE, you don't have to
include any exsl.xsl additionally. The problem is with Saxon HE, which is
by default used in C3 (2.2?).
The
Although not exactly the same way, but you can still call Java code from XSLTs
with Saxon HE 9.x. See for example:
https://github.com/alveolo/butterfly/tree/master/saxon/src/main/java/org/alveolo/butterfly/saxon/xpath
On 28 Feb 2014, at 19:15, gelo1234 gelo1...@gmail.com wrote:
The problem
