• To: "Srivathsan C" <bc_srivathsan@y...>,<xml-dev@l...>
• Subject: RE: Need help on JAXB!
• From: Jonathan Robie <jonathan.robie@d...>
• Date: Wed, 27 Aug 2003 13:44:13 -0400
• In-reply-to: <830178CE7378FC40BC6F1DDADCFDD1D1173BAF@R...>

>From: Srivathsan C [mailto:bc_srivathsan@y...]
>Sent: Wed 8/27/2003 3:38 AM
>To: xml-dev@l...
>Subject:  Need help on JAXB!
>
>         Hi All,
>
>         What is the advantages and disadvantages of using JAXB over 
> SAX/DOM parser?
>         Any sample for the same will be very useful

If your program is centered around XML, and you want to parse it and 
process it as XML, SAX and DOM are good APIs. SAX is event oriented, lean 
and faster. SAX is very fast, and if you are simply extracting or inserting 
data into documents, it is generally the tool of choice. DOM is tree 
oriented, navigational, moderately large, and strongly reflective of 
web-browser programming. Both are very popular APIs. If what you want to do 
is navigate and manipulate trees, DOM is your choice - but it can be very 
memory intensive.

JAXB does two-way mappings between XML documents and Java objects. You 
write a DTD, then the JAXB compiler creates a set of Java classes that 
contain the code used to parse XML documents that use this DTD. JAXB does 
not do tree manipulation, it places the data into Java objects, where it is 
accessed using conventional Java techniques. This makes it simpler to use 
for data-oriented applications, but it is not much good for 
document-oriented applications.

This is all discussed with concrete code examples here:

http://java.sun.com/xml/webservices.pdf

Jonathan 

• References:
  • RE: Need help on JAXB!
    • From: "Dare Obasanjo" <dareo@m...>

• Prev by Date: Re: xml taxonomy
• Next by Date: RE: XML and the Relational Model (was Re: A standard approach to glueing together ...)
• Previous by thread: RE: Need help on JAXB!
• Next by thread: RE: XML.Net find node by content and change attribute
• Index(es):
  • Date
  • Thread