[
https://issues.apache.org/jira/browse/XALANJ-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737309#comment-17737309
]
Joe Kesselman commented on XALANJ-2474:
---------------------------------------
Proposal re that last:
Currently, if an exception such as unknown-function is thrown during
dyn:evaluate(), it silently returns an empty nodeset. Uninformative at best.
Can anyone see a good reason not to change that to throw an Exception? The
EXSLT functions are specified as possibly throwing SAXException, so my current
sketch reports it as
{code:java}
(Location of error unknown)org.xml.sax.SAXNotSupportedException: dyn:evaluate()
Could not find function: document{code}
My code does use the localized form of the "Could not find function:" text, for
the obvious I18n reasons... which is why "Could" is capitalized above; I didn't
want to muck with that text. (And why I don't say "in" evaluate)
It might be possible to get the location filled in, but I think that would
require more complicated changes. This is a one-liner.
(Alternative might be to make this a nonfatal warning, but I think this one
merits demanding that the user fix the stylesheet to be compatible with Xalan.)
> document() function returns different values with xalan version 2.7.1. and
> 2.6.0.
> ---------------------------------------------------------------------------------
>
> Key: XALANJ-2474
> URL: https://issues.apache.org/jira/browse/XALANJ-2474
> Project: XalanJ2
> Issue Type: Bug
> Security Level: No security risk; visible to anyone(Ordinary problems in
> Xalan projects. Anybody can view the issue.)
> Affects Versions: 2.7.1
> Environment: Windows, using command line transform of xalan.
> Reporter: pavankumar
> Priority: Blocker
> Attachments: identitext.xsl, input.xml, jira-xalanj-2474.xml,
> jira-xalanj-2474.xslt, transform.xslt
>
>
> xslt document() function returns duplicate and improper values with 2.7.1.
> where as the same code works with 2.6.0.
> Info : document and evaluate functions are used in xslt and there were other
> slightly inconsistent behaviour also for 2 versions in terms of syntax and
> all. and xlink:href is getting nil values in 2.7.1
> document result contained by path variable line 93 - transform.xsl is the one
> causing problem. and and when printed, it outputs different values with
> different versions.
> Executed using xalan CLI
> C:\>java org.apache.xalan.xslt.Process -IN "C:\input.xml" -XSL
> "C:\transform.xslt" -OUT new.html -PARAM global.result input.xml
> attaching the files.transform.xslt and input.xml
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
For additional commands, e-mail: dev-h...@xalan.apache.org
