By chengas123
via benmccann.com
Published: Jul 26 2009 / 18:09
««
Next »
« Previous
-
100% Big Data, 0% Hadoop, 0% Java -
Project Plugh: Open Source Log Analysis
-
Useful Eclipse Plugins that didn't made it to the Top 10 list
-
Thinking in Scala: For Java Developers
-
Cloud on Merit, Not by Dictat
-
Through the eyes of sonar : equals and hashCode.
-
Like And Dislike Rating System With PHP ,MySQL and Jquery
| Subversion | |
| Written by: Lorna Jane Mitchell | |
| Featured Refcardz: Top Refcardz: | |
| 150+ Refcardz Available · Get them all | |
Comments
cj104918 replied ago:
which one is good? which one is bad. Please educate me.
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
willcode4beer replied ago:
One was written by guys in the trenches, the other by PHDs
Eric Burke replied ago:
The title doesn't really match the article.
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.
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
Voters For This Link (47)
Voters Against This Link (8)