[
https://issues.apache.org/jira/browse/XALANJ-2425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562521#action_12562521
]
Henry Zongaro commented on XALANJ-2425:
---------------------------------------
I think this bug and XALANJ-2424 illustrate serious flaws in the way XSLTC and
the Xalan-J Interpreter handle DOM nodes returned from extension functions. In
both cases they seem to be treated as if they are new nodes that are completely
separate from any nodes that the processor might previously have processed.
> Xalan's set:distinct() is broken by design
> ------------------------------------------
>
> Key: XALANJ-2425
> URL: https://issues.apache.org/jira/browse/XALANJ-2425
> Project: XalanJ2
> Issue Type: Bug
> Components: XSLTC
> Affects Versions: 2.7.1
> Environment: Any
> Reporter: Илья Казначеев
> Attachments: xml1.xml, xsl2.xsl
>
>
> Xalan's EXSLT set:distinct() is implemented in a way it is not useful, not
> usable and also confusing, not mentioning it will throw an exception if feed
> attributes list.
> See attached files, result is
> <html xmlns:set="http://exslt.org/sets";>
> <body>root</body>
> </html>
> for both libXSLT and xalan-interpreted, but it is
> <html xmlns:set="http://exslt.org/sets";>
> <body></body>
> </html>
> for XSLTC.
> Reason: Xalan does iterator for set:distinct() by creating a document,
> stuffing node list into document's element, and iterating over its children.
> This have two consequences: you can't access parent node from such node-list,
> and also see XALANJ-2424.
> See class BasisLibrary.
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
