[jdom-interest] [benchmark] JAXB VS JDOM

Trikannad, Mahesh mahesh.trikannad at capgemini.com
Wed Apr 13 11:49:03 PDT 2005

I apologize for guessing. I have not worked with JAXB, to know if it
will be faster. And I certainly do not understand how either have been

My reasoning, for JAXB being faster, is since it creates the DOM tree at
compile time, the run time overhead of creating the tree doesn't exist,
or traversing a tree , does not exist.
Why do you think it makes no sense.


-----Original Message-----
From: Elliotte Harold [mailto:elharo at metalab.unc.edu]
Sent: Wednesday, April 13, 2005 2:38 PM
To: Trikannad, Mahesh; 'jdom-interest at jdom.org'
Subject: Re: [jdom-interest] [benchmark] JAXB VS JDOM

Trikannad, Mahesh wrote:
> JAXB, involves creating implementation classes offline. It is bound to
> be faster online, compared to JDOM.

That makes no sense whatsoever. I wouldn't venture to guess whether JDOM

or JAXB is faster, but even if JAXB is faster it would have nothing to
do with what you state.

Elliotte Rusty Harold  elharo at metalab.unc.edu
XML in a Nutshell 3rd Edition Just Published!

This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient,  you are not authorized to read, print, retain, copy, disseminate,  distribute, or use this message or any part thereof. If you receive this  message in error, please notify the sender immediately and delete all  copies of this message.

More information about the jdom-interest mailing list