<flame level="slow simmer">
JDOM is not a W3C specification. It's in competition with the W3C DOM.
Some of us have strong philosophical objections to JDOM, since its
implementation as classes rather than interfaces imposes some serious
problems when trying to integrate it with other code. (Basically, there is
only one JDOM implementation.) There are some JDOM derivitives/competetors
which do define themselves as interfaces; I've yet to see one that I
thought delivered significant value, but it's been a while since I looked
at this. Their main advantage, if it is one, seems to be just that they're
more Java-specific.
By all means, look at it -- but realize that you're buying nonportability
of your code in exchange for whatever advantages it might or might not
offer.
</flame>
______________________________________
Joe Kesselman, IBM Next-Generation Web Technologies: XML, XSL and more.
"The world changed profoundly and unpredictably the day Tim Berners Lee
got bitten by a radioactive spider." -- Rafe Culpin, in r.m.filk
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
