[jdom-interest] Content as a Text Node (was JDOM JSR)

philip.nelson at omniresources.com philip.nelson at omniresources.com
Fri May 18 12:36:19 PDT 2001

I didn't think I'd see myself writing these words but...

I agree completely with this idea.  The api most people use with jdom to get
string content doesn't have to change.  Not having a String in the mixed
content will not affect many existing apps I would think.

Basically, if there is *any* valid reason to use a node like interface,
whether you do it decorated, subclassed, whatever, you will need this
feature to avoid clumsy special casing.  Elliotte brought up full unicode
support, very important to some people.  A text class would be required for
any deferred build option I would think. What would the downsides be?
Memory? Construction speed?  I think this idea maintains the simplicity and
extends the usefulness. 

Maybe more people would think we're cool too.

More information about the jdom-interest mailing list