6

I need to process an XML DOM, preferably with JDOM, where I can do XPath search on nodes. I know the node names or paths, but I want to ignore namespaces completely because sometimes the document comes with namespaces, sometimes without, and I can't rely on specific values. Is that possible? How?

kaya3
  • 47,440
  • 4
  • 68
  • 97
AdSR
  • 2,097
  • 3
  • 15
  • 9
  • Rather than ignoring them you can also retrieve and then use them. See [How to retrieve namespaces in XML files using Xpath](http://stackoverflow.com/q/122463/507761) – Matthew Read Mar 13 '12 at 21:50

4 Answers4

18
/ns:foo/ns:bar/@baz

becomes

/*[local-name() = 'foo']/*[local-name() = 'bar']/@baz

You get the point. Don't expect that to be lightning-fast either.

Tomalak
  • 332,285
  • 67
  • 532
  • 628
  • I tried the solution from here: http://stackoverflow.com/questions/543049/default-xml-namespace-jdom-and-xpath It is much simpler and works as long as the root element has any namespace declared. But if there is no namespace, it doesn't - so either I use the above, or I have a separate solution for no namespaces. – AdSR Apr 09 '10 at 14:36
  • @AdSR: Your question seemed to imply that you have no knowledge of the namespace state of your input documents & they come at random. In this case, the above is the "safest", as in: it will always work, but you lose the ability to make a difference between `x:foo` and `ns:foo`. – Tomalak Apr 09 '10 at 15:25
  • Thanks, this solution worked for me in jdom 1.x (/*:foo didn't work). – expert Aug 29 '12 at 16:42
4

Here is a jDOM2 solution that has been running in a production setting for a year with no trouble.

public class JdomHelper {

    private static final SAXHandlerFactory FACTORY = new SAXHandlerFactory() {
        @Override
        public SAXHandler createSAXHandler(JDOMFactory factory) {
            return new SAXHandler() {
                @Override
                public void startElement(
                        String namespaceURI, String localName, String qName, Attributes atts) throws SAXException {
                    super.startElement("", localName, qName, atts);
                }
                @Override
                public void startPrefixMapping(String prefix, String uri) throws SAXException {
                    return;
                }
            };
        }
    };


    /** Get a {@code SAXBuilder} that ignores namespaces.
     * Any namespaces present in the xml input to this builder will be omitted from the resulting {@code Document}. */
    public static SAXBuilder getSAXBuilder() {
        // Note: SAXBuilder is NOT thread-safe, so we instantiate a new one for every call.
        SAXBuilder saxBuilder = new SAXBuilder();
        saxBuilder.setSAXHandlerFactory(FACTORY);
        return saxBuilder;
    }

}
jaco0646
  • 15,303
  • 7
  • 59
  • 83
4

I know this question is a little old, but for those viewing this later, you can override a few JDOM default classes to effectively make it ignore namespaces as well. You can pass your own JDOMFactory implementation to the SAXBuilder that ignores all Namespace values passed into it.

Then override the SAXBuilder class and implement the createContentHandler method so that it returns a SAXHandler with a blank definition for the startPrefixMapping method.

I haven't used this in a production setting so caveat emptor, but I have verified that it does work on some quick and dirty XML stuff I've done.

jhulford
  • 98
  • 7
4

You can use /*:foo (XPath 2.0 or higher) or /yournamespace:* as explained here.

The first variant selects all nodes with the matching name, regardless of what namespace they belong to, including having no namespace. The latter selects all nodes belonging to a specific namespace, regardless of the node name.

akostadinov
  • 17,364
  • 6
  • 77
  • 85
  • @user520567: Your second QName test (`NS:*`) is valid XPath 1.0/2.0, but the first one (`*:Name`) is only valid XPath 2.0. Without this information your answer has less value... –  Nov 25 '10 at 21:53
  • It is named xpath2-intro ;) And actually question is answered by the first expression only. But sure I should have written that. – akostadinov Dec 02 '10 at 07:23