[jdom-interest] Should I convert to/from org.jdom.Document

Naresh Bhatia NBhatia at sapient.com
Sat Jan 19 12:46:18 PST 2002

That's definately an intresting approach - keeps the JDOM model intact and
no translation involved. Thank Anthony.
Any other thoughts from the group?

-----Original Message-----
From: Anthony Eden [mailto:aeden at signaturedomains.com]
Sent: Saturday, January 19, 2002 8:08 AM
To: jdom-interest at jdom.org
Subject: RE: [jdom-interest] Should I convert to/from org.jdom.Document

I primarily use JDOM for loading configuration data.  To that end I have a
Configuration interface and then one of the concrete implementations wraps a
JDOM document.  The interface includes methods like getChildren(),
getChildValue(), getValue(), etc.  I can then use different implementations
(such as pull data from a database) very easily.
Anthony Eden

-----Original Message-----
From: jdom-interest-admin at jdom.org [mailto:jdom-interest-admin at jdom.org] On
Behalf Of Naresh Bhatia
Sent: Friday, January 18, 2002 4:17 PM
To: 'jdom-interest at jdom.org'
Subject: [jdom-interest] Should I convert to/from org.jdom.Document


I have a quick design question for the group. When using an XML parser such
as JDOM, is it better for the application to work directly with the document
tree (such as org.jdom.Document) or should it use an application specific
model and convert to/from the document tree? What are the pros/cons of the
two approaches, where does one make sense over the other?

Naresh Bhatia 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://jdom.org/pipermail/jdom-interest/attachments/20020119/9cb673a0/attachment.htm

More information about the jdom-interest mailing list