To explain why this is happening: if you're running a site like xsltfiddle that
can execute arbitrary user-submitted XSLT code on your server, then (a) you
need to disable calls on Java extension functions, because otherwise the XSLT
code could cause havoc by displaying arbitrary system files on the server (or
modifying them), and (b) you need to disable xsl;result-document because that
can write (or overwrite) arbitrary files on the server. Saxon puts both these
controls under a single configuration option, which xsltfiddle has (rightly)
set.
For the record, you should also supply a URIResolver, CollectionResolver, and
UnparsedTextResolver that prevent access to local filestore.
Michael Kay
Saxonica
On 14 May 2019, at 06:17, Martin Honnen martin(_dot_)honnen(_at_)gmx(_dot_)de
<xsl-list-service(_at_)lists(_dot_)mulberrytech(_dot_)com> wrote:
Am 14.05.2019 um 02:47 schrieb Manuel Souto Pico
terminolator(_at_)gmail(_dot_)com:
I get: Stylesheet compilation failed with 1 error(s):
Error 1 at line 27:48 : xsl:result-document is disabled when extension
functions are disabled
https://xsltfiddle.liberty-development.net/ej9EGcD/10
That is a limitation of the tool, not a limitation of Terry's code, if
you change the one template he had using "xsl:result-document" to
<xsl:template match="/">
<xsl:apply-templates/>
</xsl:template>
you should get it work with xsltfiddle.
--~----------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
EasyUnsubscribe: http://lists.mulberrytech.com/unsub/xsl-list/1167547
or by email: xsl-list-unsub(_at_)lists(_dot_)mulberrytech(_dot_)com
--~--