1) At the moment, struts-support.xsl uses a Xalan extension, so it is not possible without writing some Java code to use the extension with Saxon or XSLTC. It is definitely doable in theory, and it does make sense to be able to use those extensions from multiple XSLT transformers.
Our experience is that Saxon most of the time performs similarly to Xalan.
2) With XSLT 1.0 import, include, and the document() function with static URLs do impact caching, in that if the imported or included document is changed, the stylesheet will be re-executed.
If the document() function is passed a dynamic URL, the stylesheet will be re-executed each time.
Those caching features are currently not supported with XSLT 2.0 in OXF.
-Erik
Kesara Kudalugodaarachchi wrote:
> Hi,
> 1. Is it possible to use a faster transformer (or even xsltc), other
> than xalan in starts integrated mode?
> The "struts-support.xsl" specifically uses xalan namespaces !!
> When we tried Saxon with OXF version 2.0.2 it failed with the
> following error
>
> 2003-10-13 17:52:19,371 ERROR org.orbeon.oxf.servlet.ProcessorService - Exception at oxf:/default/xsl/admin/login.xsl,line 17, column -1;
> SystemID: oxf:/struts/struts-support.xsl; Line#: 37; Column#: -1
> javax.xml.transform.TransformerException: Unknown extension element
> at com.icl.saxon.style.StyleElement.styleError(StyleElement.java:806)
>
>
> 2. How does the import/include statements and "document" function in
> XSL pages affect caching?
>
> Regards,
> Kesara.
_______________________________________________ oxf-users mailing list [EMAIL PROTECTED] http://mail.orbeon.com/mailman/listinfo/oxf-users
