[
https://issues.apache.org/jira/browse/XALANJ-2524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924176#action_12924176
]
Mukul Gandhi commented on XALANJ-2524:
--------------------------------------
If template "foo" now indeed calls itself recursively, then this is ok (it
didn't before, see mailing list thread).
[mukul] it does as I reported.
WRT your question: I was testing something that works in Saxon/xsltproc, and
noticed the difference in Xalan-J (which my customer uses because of FOP's
defaults). That's why I investigated and came up with the small test case.
[mukul] that's fine and I believe this is appreciated by Xalan community.
In the meantime, I refactored my code as it didn't need recursion anyway. But I
thought that a reproduceable problem should be reported anyway, and that's what
I did.
[mukul] I'm glad the problem is resolved :)
> applying exslt:node-set to a node set yields something that is not a node set
> -----------------------------------------------------------------------------
>
> Key: XALANJ-2524
> URL: https://issues.apache.org/jira/browse/XALANJ-2524
> Project: XalanJ2
> Issue Type: Bug
> Security Level: No security risk; visible to anyone(Ordinary problems in
> Xalan projects. Anybody can view the issue.)
> Components: Xalan-extensions
> Affects Versions: 2.7.1
> Reporter: Julian Reschke
> Priority: Minor
> Attachments: patch_xalanj-2524.txt
>
>
> Applying the exslt:node-set extension to something that already is a node set
> yields a non-node set result.
> This is a bug according to
> <http://exslt.org/exsl/functions/node-set/exsl.node-set.html>:
> "If the argument is a node-set already, it is simply returned as is."
> Test case:
> <?xml version="1.0" encoding="UTF-8"?>
> <xsl:stylesheet version="1.0"
> xmlns:xsl="http://www.w3.org/1999/XSL/Transform";
> xmlns:exslt="http://exslt.org/common";
> >
> <xsl:output method="text"/>
> <xsl:template match="/">
>
> <xsl:variable name="t">
> <root>
> <x>1</x>
> <x>2</x>
> <x>3</x>
> </root>
> </xsl:variable>
> <xsl:variable name="tns1" select="exslt:node-set($t)/root/x"/>
> <xsl:variable name="tns2" select="exslt:node-set($tns1)"/>
>
> Type of t: <xsl:value-of select="exslt:object-type($t)"/>
> Type of tns1: <xsl:value-of select="exslt:object-type($tns1)"/>
> Name of tns2: <xsl:value-of select="exslt:object-type($tns2)"/>
>
> </xsl:template>
> </xsl:stylesheet>
> This yields the expected result in xsltproc, Saxon 6.* and XSLTC, but not in
> Xalan-J.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscr...@xml.apache.org
For additional commands, e-mail: xalan-dev-h...@xml.apache.org
