[
https://issues.apache.org/jira/browse/JXPATH-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Benson resolved JXPATH-92.
-------------------------------
Resolution: Won't Fix
Sergey, I have spent a lot of time going over this. In theory I wouldn't have
a problem with supporting pointers as variable values, BUT I do think that
transparently converting these to the pointers in question is a matter of
opinion as to whether such behavior would be expected, so my decision is that
that behavior, and the subsequent "proper sorting" you are after, will NOT be
implemented. This being the case I can't see much purpose in allowing pointers
as variable values after all; my advice here is to explore dynamically building
your XPath expressions to always use the proper path to an object.
> Allow to use NodePointers as variable values and preserve tree position
> information
> -----------------------------------------------------------------------------------
>
> Key: JXPATH-92
> URL: https://issues.apache.org/jira/browse/JXPATH-92
> Project: Commons JXPath
> Issue Type: Improvement
> Affects Versions: 1.2 Final
> Reporter: Sergey Vladimirov
> Attachments: hack-patch.txt, VariablePointerTestCase.java
>
>
> Moved from JXPATH-89
> It should be possible to return NodePointer as variable value and use such
> node pointer as part of original tree to sort and comapre nodes.
--
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]
