Link Details

A comparison between two APIs. One good. And one bad.

Posted by chengas123  |   Jul 26 2009 / 18:09

Add your comment


Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.

Comments

User 62182 avatar

cj104918 replied ago:

which one is good? which one is bad. Please educate me.

Reply 1 votes
User 251548 avatar

Jawher replied ago:

I more than agree : the w3c dom api is a pain in the ass to use, whereas dom4j (and jdom) are much more usable and targeted for human beings

Reply 5 votes
User 209464 avatar

willcode4beer replied ago:

One was written by guys in the trenches, the other by PHDs

Reply 1 votes
User 230306 avatar

Eric Burke replied ago:

The title doesn't really match the article.

Reply 0 votes
User 222305 avatar

middlec replied ago:

So to sum it up dom4j good, xerces bad?! WTF? I hate to be negative, but this really was bad. There was absolutely nothing in there to give you guidelines on building an api. Exactly no insight.

Reply 0 votes
User 272290 avatar

chengas123 replied ago:

not dom4j good, xerces bad. dom4j user-friendly api, xerces pain in the butt api. i use xerces over dom4j most of the time, but am incredibly frustrated by the difficulty and verbosity of a number of simple tasks when using it

Reply 0 votes

Recommended Links

Scala
Written by: Ryan Knight
Featured Refcardz: Top Refcardz:
  1. Apache Hadoop
  2. Play
  3. Akka
  4. Debugging JavaScript
  5. Design Patterns
  1. Apache Hadoop
  2. REST
  3. Java
  4. Git
  5. Java Performance
Connect with DZone