简体   繁体   English

从 ANT 运行 Saxon 11 时,unparsed-text() 函数不起作用

[英]The unparsed-text() function doesn't work when Saxon 11 is run from ANT

I'm using Saxon 11 from ANT .我正在使用来自ANTSaxon 11 XSLT transformation works, except that the unparsed-text() function triggers a fatal error. XSLT 转换有效,但unparsed-text()函数会触发致命错误。 Error message:错误信息:

Resolver for unparsed-text() returned non-StreamSource;

Software: SaxonEE11-3J, Ant 1.10.3, Java openjdk 1.8.0.191 win64, Windows 10 Pro软件:SaxonEE11-3J、Ant 1.10.3、Java openjdk 1.8.0.191 win64、Windows 10 Pro

Ant code:蚂蚁代码:

<path id="xslt.saxonEE.classpath">
    <fileset dir="D:/SaxonEE11-3J">
        <include name="*.jar"/>
    </fileset>
</path>

<target name="target-test">
    <xslt in="C:/input.xml" style="D:/test.xsl" out="C:/test.xml" force="true" processor="trax">
        <classpath refid="xslt.saxonEE.classpath"/>
        <factory name="com.saxonica.config.EnterpriseTransformerFactory">
            <attribute name="http://saxon.sf.net/feature/ignoreSAXSourceParser" value="true"/>
            <!--<attribute name="http://saxon.sf.net/feature/unparsedTextURIResolverClass" value="net.sf.saxon.lib.StandardUnparsedTextResolver"/>-->
        </factory>
    </xslt>
</target>

As Mike observes, the XSLT 1.0 based interfaces are getting a bit long in the tooth.正如 Mike 所观察到的,基于 XSLT 1.0 的接口已经有点长了。 However, I think it would probably be possible to support this request.但是,我认为可能会支持这个请求。 I've opened bug 5582 to track it.我已经打开了错误 5582来跟踪它。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM