Comments on: Dom4j + XPath + TagSoup - Namespaces = sweet!

By: Kelvin

Kelvin — Wed, 07 Jul 2010 05:05:00 +0000

@Ken - that’s a great idea with SAXReader.setXMLFilter(). Probably much cleaner than the method I posted about.

By: Ken Krugler

Ken Krugler — Wed, 07 Jul 2010 00:58:26 +0000

Hi Kelvin,

I’ve solved this same issue two different ways in the past.

Easiest (brute force) is by calling SAXReader.setXMLFilter() with a filter, where that filter strips off namespaces.

The other approach is to use a utility routine that re-writes the XPath path with the required namespace identifier. Though I wound up having to also set the namespace context (XPath.setNamespaceContext(new SimpleNamespaceContext(map))) with a map from the identifier to the full xmlns://.

-- Ken

By: Extraer contenido HTML mediante consultas xpath con dom4j y Tagsoup « Un Beagle y Yo

Mon, 17 May 2010 22:46:29 +0000

[...] entrada para eliminar el prefijo html de las [...]

By: Parsing Real World HTML with XPath support - Java Forums

Parsing Real World HTML with XPath support - Java Forums — Wed, 12 May 2010 09:46:23 +0000

[...] Using XPath on real-world HTML documents seems to work well except the following namespace problem: Dom4j + XPath + TagSoup – Namespaces = sweet! :: Kelvin Tan - Lucene Solr Nutch Consultant It seems other parsers are available: Open Source HTML Parsers in Java some of which support [...]

By: dis

dis — Sat, 08 May 2010 21:26:14 +0000

thanks for those parser’s parameters. worked for me very well. you post saved my life!