cxf-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Kulp <>
Subject Re: Switching from JAXB to XMLBeans data binding
Date Thu, 21 May 2009 20:38:24 GMT

One more comment:
There are a lot of things in CXF that won't work without the JAXB jar.   I'm 
not even sure if config parsing or wsdl parsing will work with JAXB.   Thus, 
you may not be able to get rid of jaxb anyway.

That said, if you use Java 6, it SHOULD work with the jaxb stuff built into 
Java 6.  Thus, if you app requires Java 6 update 4 or later, you should be 
able to use JAXB, but not really "ship" JAXB.


On Thu May 21 2009 4:36:02 pm Daniel Kulp wrote:
> On Thu May 21 2009 4:00:44 am Stevo Slavić wrote:
> > Hello CXF Users,
> >
> > Because of licensing issues when using JAXB, I have to switch to XMLBeans
> > as data binding provider.
> Interesting.      CDDL is normally not a "bad" license.
> > Before making a switch, are there any known
> > limitations or issues this switch could bring (e.g. lack or limitted
> > functionality, security, etc.)?
> The main one I know about is that MTOM will no longer work.   XMLBeans
> doesn't provide any way to do mtom.    Security and such should work fine.
> The main thing is that the xmlbeans databindind is not nearly as well
> tested as JAXB.   The tooling is more limited.   Etc....
> That said, I do encourage you to try it and log any bugs/issues you may
> encounter.
> > Also, is it known why it was decided to use
> > JAXB as default data binding?
> Well.   JAX-WS requires JAXB.   Thus, to pass the JAX-WS TCK, we need to
> have JAXB working.   In general, JAXB performs fairly well, supports a very
> large percent of schema, and provides the apis and stuff needed to do
> everything we need (like MTOM).

Daniel Kulp

View raw message