Comments on: Showdown – Java HTML Parsing Comparison

By: Victor

Victor — Sat, 25 Jun 2011 08:13:31 +0000

Thanks for this excellent article. After 3 years of the initial comparison, the results are still useful to choose the appropriate html parser for our needs. I will use HTMLCleaner by the way…

By: marcelo camanho

marcelo camanho — Sat, 23 Apr 2011 00:34:05 +0000

utkarsh, you can use the following:

CleanerProperties props = new CleanerProperties();
//not sure if you will need it, but i needed it..
props.setNamespacesAware(false);

DomSerializer dom = new DomSerializer(props);
Document doc = dom.createDOM(clean);

By: utkarsh

utkarsh — Thu, 07 Apr 2011 05:05:41 +0000

Hi Ben in your code for Html Cleaner you are using
document=cleaner.createDOM();
However this function is not present in HTMLCleaner class
So, please help me.
Thanks

By: utkarsh

utkarsh — Tue, 22 Mar 2011 06:59:59 +0000

thanks Ben

By: Ben

Ben — Mon, 21 Mar 2011 17:52:10 +0000

Hi Utkarsh,
urlIs is a java.io.InputStream. One way of getting an InputStream is to call URL.openStream(). If you’re reading from files on disk you’ll probably want to use a java.io.FileInputStream.

By: utkarsh

utkarsh — Mon, 21 Mar 2011 11:59:52 +0000

What is urlIS here ? which class’s object is it.
actually i am trying to parse an html page stored on disk .
how to supply the FileReader object to HTMLCleaner Constructor

By: Mario Gaitán

Mario Gaitán — Wed, 02 Mar 2011 04:39:50 +0000

Thanks for the post, great comparison!!!

By: David

David — Mon, 17 Jan 2011 06:52:46 +0000

Thanks to all for your posts and your time !!!
I really appreciate it !

By: Ankur

Ankur — Fri, 10 Dec 2010 20:37:56 +0000

Hi,

Can someone please help me with the following problem that I’m facing ?

I am parsing certain html pages. For a best effort , I’m using Neko, and if Neko fails, my code will switch to JTidy. After parsing, I use xpath to extract some information in the page. The problem is that Neko prefixes “xhtml” before every element in the parsed DOM. So I have to specify this prefix in the Xpath also (Eg, //xhtml:a/@href ) Because of this problem, I’m not able to use a common xpath for extraction, while not worrying about which parser created the DOM ( Neko or JTidy), Please help.

Thanks,
Ankur.

By: Compare Excel Sheets

Compare Excel Sheets — Fri, 13 Aug 2010 08:58:57 +0000

very nice resource for web developers. Thanks dude for valuable information.