Mailing-List: contact users-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cxf.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
From: Daniel Kulp <dkulp@apache.org>
To: users@cxf.apache.org
Subject: Re: Switching from JAXB to XMLBeans data binding
Date: Thu, 21 May 2009 16:36:02 -0400
User-Agent: KMail/1.11.3 (Linux/2.6.29-gentoo; KDE/4.2.3; x86_64; ; )
Cc: Stevo =?utf-8?q?Slavi=C4=87?= <sslavic@gmail.com>
References: <7459404c0905210100u6a52fa2dje1fd3c90387d5b7e@mail.gmail.com>
In-Reply-To: <7459404c0905210100u6a52fa2dje1fd3c90387d5b7e@mail.gmail.com>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <200905211636.03081.dkulp@apache.org>

On Thu May 21 2009 4:00:44 am Stevo Slavi=C4=87 wrote:
> Hello CXF Users,
>
> Because of licensing issues when using JAXB, I have to switch to XMLBeans
> as data binding provider.=20

Interesting.      CDDL is normally not a "bad" license. =20

> Before making a switch, are there any known
> limitations or issues this switch could bring (e.g. lack or limitted
> functionality, security, etc.)?=20

The main one I know about is that MTOM will no longer work.   XMLBeans does=
n't=20
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 teste=
d=20
as JAXB.   The tooling is more limited.   Etc....   =20

That said, I do encourage you to try it and log any bugs/issues you may=20
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 ha=
ve=20
JAXB working.   In general, JAXB performs fairly well, supports a very larg=
e=20
percent of schema, and provides the apis and stuff needed to do everything =
we=20
need (like MTOM).


=2D-=20
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog