Java vs. xml storyline: JAXB and Jaxp

When I first started using Java, I would sometimes consider using XML to store data, which would normally use the DOM in JAXP or the SAX parser package to crud XML files. Later, the Web service was very well formatted document, WSDL, XSD, which is very suitable for the automatic generation of code, so there is JAXB, through the annotation to facilitate the conversion between XML and Java class.

jaxp (Java API for XML processing) Dom ( document object Model " treats the whole XML as object processing, which is very convenient for random reading and writing. However, if the XML file is large, it may be problematic for memory consumption, SAX (simple API FOR XML ) treats all nodes in XML as event handlers (org.xml.sax.helpers.defaulthandler ", the sequential reading of the XML file is much better than DOM and consumes less memory faster.

JAXP also has a very useful 2 members, XSTL (extensible Stylesheet Language Transformations) in Java to implement XML and other formats of conversion and Stax (streaming API for XML) is similar to sax in that it handles XML files in a streaming fashion while actively pulling the data instead of passively waiting for the event to arrive.

JAXP's API can be said to be the direct processing of XML low-level API, for WebService and ORM Services, direct use is too complex, in order to further simplify the work of programmers, JAXB (Java Architecture for XML Binding ) appears as a special API (belonging to thejavax.xml.bind的一部分) ，using the XML document'sXML SchemaDefinition (XSD), in JavaUse annotations to implement XML document and Java Object Model mapping.

In the next series, the main thing is to write how you can transform XML and Java objects through JAXB.

Java vs. xml storyline: JAXB and Jaxp