[jdom-interest] Is JDOM dying?

Malachi de AElfweald malachi at tremerechantry.com
Fri Mar 14 23:19:35 PST 2003

I am actually having much luck with JAXB so far.  Within 24 hours of asking
how to fix the namespace output, SUN submitted preliminary code for me to
test to see if it fixed my problem.  Within the next 24 hours, they 
another remake of it to further make it like I expected.

With JDOM, I just have to triple how much code I write to get the correct 
behavior --
or just don't use Namespaces.


On Fri, 14 Mar 2003 10:22:42 -0500, Frank Sauer <Frank.Sauer at trcinc.com> 

> Apparently, some people are doing exactly that;
> they're picking JAXB over JDOM....
> -----Original Message-----
> From: Elliotte Rusty Harold [mailto:elharo at metalab.unc.edu]
> Sent: Friday, March 14, 2003 7:47 AM
> To: stephan at ncube.de; malachi at tremerechantry.com
> Cc: JDOM
> Subject: Re: [jdom-interest] Is JDOM dying?
> At 8:56 AM +0100 3/14/03, Stephan Trebels wrote:
>> Would it be a workable compromise  to have a Namespace.INHERIT for an
>> Element as a possible namespace argument?
> I wouldn't accept such a compromise. It's ugly. Right now the JDOM 
> namespace story is clean and consistent. This proposal says it changes 
> depending on whether or not you set Namespace.INHERIT. Too many options 
> just create a baroque API that's hard to learn, hard to teach, and hard 
> to use. Generally when faced with two possible ways of accomplishing 
> something, it's better to pick one than to pick both.


More information about the jdom-interest mailing list