Link Details

Link 207700 thumbnail
User 272290 avatar

By chengas123
via benmccann.com
Published: Jul 26 2009 / 18:09

A comparison between two APIs. One good. And one bad.
  • 47
  • 8
  • 6356
  • 2

Comments

Add your comment
User 62182 avatar

cj104918 replied ago:

1 votes Vote down Vote up Reply

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

User 251548 avatar

Jawher replied ago:

5 votes Vote down Vote up Reply

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

User 209464 avatar

willcode4beer replied ago:

1 votes Vote down Vote up Reply

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

User 230306 avatar

Eric Burke replied ago:

0 votes Vote down Vote up Reply

The title doesn't really match the article.

User 222305 avatar

middlec replied ago:

0 votes Vote down Vote up Reply

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.

User 272290 avatar

chengas123 replied ago:

0 votes Vote down Vote up Reply

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

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.

Debugging JavaScript
Written by: Ashutosh Sharma
Featured Refcardz: Top Refcardz:
  1. Design Patterns
  2. OO JS
  3. Cont. Delivery
  4. Java EE7
  5. HTML5 Mobile
  1. Java EE7
  2. Spring Annotations
  3. Git
  4. Java
  5. REST