Skip to Content.
Sympa Menu

xom-interest - [XOM-interest] XOM design

xom-interest AT

Subject: XOM API for Processing XML with Java

List archive

Chronological Thread  
  • From: Edwin Goei <edwingo AT>
  • To: Elliotte Rusty Harold <elharo AT>
  • Cc: xom-interest AT
  • Subject: [XOM-interest] XOM design
  • Date: Thu, 28 Nov 2002 09:38:12 -0800


I wrote you earlier and hope you now have some time to share your views in writing on the following points...

I am comparing DOM, JDOM, DOM4J, and XOM. So I was looking over your
XOM presentation and noticed a few features of your API but no
justification for them on your site. You state:

1) DOM: Interfaces are a bad idea
DOM4J: Uses interfaces instead of classes

2) XOM does not allow method call chaining

3) JDOM: Setter methods don't return void

Could you explain why you think the above characteristics are bad in a
XML tree API? For example, why do you think method call chaining is a
bad idea? There are classes in JDK 1.4 like StringBuffer and nio that
support this paradigm.


  • [XOM-interest] XOM design, Edwin Goei, 11/28/2002

Archive powered by MHonArc 2.6.24.

Top of Page