A question regarding namespace nodes appearing in DOMXPath result node-sets:
It seems to me that an XPath expression like ".//@*", applied to a document using the org.jaxen.dom.DOMXPath class, should not include org.w3c.Attr nodes for namespace declarations in the source document (at least w.r.t. the XPath data model). Moreover, an XPath expression like "(.//@* | .//namespace::*)" results in a node-set including two nodes for the same markup (one org.w3c.dom.Attr and one org.jaxen.dom.NamespaceNode) for each namespace declaration, which isn't really in the spirit of the XPath node-set. I would think that, in the XPath data model, the Attr node would not be present in the result node-set, even though the underlying DOM implementation returns it in lieu of a namespace node. Any thoughts on this? Ari Kermaier [EMAIL PROTECTED] Senior Software Engineer Phaos Technology Corp. http://www.phaos.com/ ------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 _______________________________________________ Jaxen-interest mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jaxen-interest
