> A better example of what I find weird would be that if you have an > entire document that is in the xhtml namespace and then one node that is > in the "" namespace, then any, 'normal' xpath expressions.(ones without > namespace specification. eg: //[EMAIL PROTECTED]'blah'] would ONLY consider > the one that has no namespace and would skip over all the standard xhtml > document tags.
I think I understand your concerns. At the moment the Jaxen implementation provides default namespace prefix mappings, based on the namespaces and their prefixes defined on the context element. (Note: I don't think anybody should rely on this mechanism, since this would make the code less portable) I now think that your reasoning is that if they can do this for the prefixed namespaces why not also do the same thing for the default namespace? (I think I agree with this) Regards, Edwin -- http://www.edankert.com/ ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ dom4j-user mailing list dom4j-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dom4j-user
