saxon 11从蚂蚁运行时,无效的text()函数无效
我正在使用 Saxon 11 来自 ant 。 XSLT转换有效,除了 Unparsed-Text()函数触发致命误差。 错误消息:
Resolver for unparsed-text() returned non-StreamSource;
软件:SAXONEE11-3J,ANT 1.10.3,Java OpenJDK 1.8.0.191 Win64,Windows 10 Pro
Ant代码:
<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>
I'm using Saxon 11 from ANT. XSLT transformation works, except that the unparsed-text() function triggers a fatal error.
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
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>
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
正如迈克所观察到的那样,基于XSLT 1.0的界面在牙齿上越长一些。但是,我认为可能支持此请求。我已经打开了 bug 5582 进行跟踪。
As Mike observes, the XSLT 1.0 based interfaces are getting a bit long in the tooth. However, I think it would probably be possible to support this request. I've opened bug 5582 to track it.