JSR222 specifies the Java Architecture for XML Binding (JAXB) 2.0. JAXB 2.0 specification is implemented in Java Web Services Developer Pack (JWSDP) 2.0. JAXB 2.0 has some new features that facilitate the marshalling and unmarshalling of an XML document. I have used both JAXB 1.0 and JAXB 2.0 and have found that JAXB 2.0 …
Please use mor recent versions of the JAXB RI
JWSDP 2.0 contains an ancient version of the JAXB RI. It's a pre-final early access release version, and in fact there's some significant differences between this version and the final version.
If you are interested in using JAXB 2.0, please go to http://jaxb.dev.java.net/ and download the latest 2.0.2 from there, instead of JWSDP 2.0
Too late and not JRE backwards compatible
This is years too late, it requires Java 1.5 and above to run, not good. I have successfuly used Castor for years (because JAXB1.0 was so dire) and have to use Java 1.4 at work, so this is a non-event to me.
RE:Please use mor recent versions of the JAXB RI
The JWSDP 2.0 version of JAXB 2.0 is used, so that JAXB may be used with other web services APIs. JWSDP 2.0 contains JAXB 2.0 EA3. Between JAXB 2.0 ea3 and JAXB 2.02 a few bug fixes and features have been added.
For notable changes between JAXB 2.0 ea 3 and JAXB 2.02 please refer
RE:Too late and not JRE backwards compatible
As mentioned in the tutorial, JDK 5.0 is required for JAXB 2.0. If JDK 1.4 has to be used JAXB 1.0, XMLBeans, or Castor may be used.
JAXB 2.02 may also be used separately as suggested by Kohsuke Kawaguchi.
The JAXB 2.0 implemenetation in JWSDP 2.0 or Project GlassFish is recommended if other web service APIs(the "integrated stack") are also used.
"The current release of Java Web Services Developer Pack, Version 2.0, contains the new JAX-WS 2.0 EA, JAXB 2.0 EA, and SAAJ 1.3 EA implementations, the "integrated stack" for Web services. These components are now available as FCS-quality releases in Project GlassFish. These three components represent a new architecture that establishes more logical relationships between Web services description, data binding, and SOAP attachment processing. The result is that deploying Web services with the integrated stack is easier, more efficient, and more reliable."