I've looked into this further. The problem appears to be linked to the nature of the context node, not to the question of default namespaces.
Appologies, -bryan -----Original Message----- From: Bryan Thompson [mailto:[EMAIL PROTECTED] Sent: Monday, March 03, 2003 7:46 PM To: [EMAIL PROTECTED] Subject: default namespaces and xpath Hello, I would like to clarify something here. It appears to me that dom4j, with Jaxen supplying namespace support, is not identifying elements in the default namespace when: - There IS a namespace context on the XPath object and - The element is identified in the XPath expression using that namespace. I don't believe that I've seen people talk about this case. For example: Map namespaceURIs = new HashMap(); namespaceURIs.put( "foo", "http://www.foo.org/the-foo-namespace"; ); XPath xpath = doc.createXPath( "foo:bar" ); xpath.setNamespaceURIs( namespaceURIs ); if( ! xpath.matches( doc ) ) ...; Appears to NOT match a document: <bar xmlns="http://www.foo.org/the-foo-namespace"/> Thanks, -bryan ------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com _______________________________________________ dom4j-dev mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dom4j-dev
