You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xalan.apache.org by bu...@apache.org on 2002/01/04 15:12:03 UTC
DO NOT REPLY [Bug 5691] New: -
Add a DOM-node XPath generator utility
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5691>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5691
Add a DOM-node XPath generator utility
Summary: Add a DOM-node XPath generator utility
Product: XalanJ2
Version: CurrentCVS
Platform: All
OS/Version: All
Status: NEW
Severity: Enhancement
Priority: Other
Component: org.apache.xpath
AssignedTo: xalan-dev@xml.apache.org
ReportedBy: keshlam@us.ibm.com
See mailing list archives for past discussion. A simple
/x:foo[1]/y:bar[3]/x:bax[2] path (with associated namespace context) is almost
trivial to generate, so there isn't a strong need for Xalan to provide this
operation... but it would be a nice convenience to offer.
Handling the namespaces properly is the most complicated part.
If we wanted to get fancy, we could take it up a notch and generate paths from
one node to another rather than always from root. But at that point I believe
the variability of XPaths, and questions about which choices will be most robust
under actual use of this particular document, become large enough issues that we
should tell the user to code their own.