You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by ku...@wipro.com on 2006/12/04 13:45:54 UTC
[Axis2] Which data binding to use
Hi *,
Axis supports four flavours of databinding
ADB,
XMLBeans
Jibx
jaxme
Is there any document explaining about these data bindings. On what
basis one should choose the Data binding for the webservice.
Has anyone has come across the document detailing the bindings, its
advantage, disadvantage.
Thanks in advance for your help.
_________________________________________________
Thanks & Regards,
Vinodh
The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments.
WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
www.wipro.com
Re: [Axis2] Which data binding to use
Posted by Paul Fremantle <pz...@gmail.com>.
Vinodh
This is pretty hard to answer, because they all have pluses and minuses. As
well people have personal preferences.
Here are some thoughts - some of which might be wrong, so everyone please
kick in with improvements or corrections.
ADB. This is the default and comes built into Axis2. It has some nice
options, like being able to embed the generated bindings as inner classes in
the stub (keeps everything neat). It also seems pretty fast. It doesn't yet
have 100% schema support. It also doesn't generate the cleanest or prettiest
code.
JAXB2 (jaxbri setting). This is still early access, but seems to work well
with the latest 1.1.1 nightlies from my experience. Being a standard it has
some benefits, and also it generates really clean nice code. My own testing
puts it within 5% of ADB for performance. I believe this pre-reqs JDK1.5.
XMLBeans is a very stable very complete package. It has very very good
schema support. It also generates lots of classes plus .xsb files that need
to be in the classpath. Performance is slightly slower than ADB in my own
tests.
JIBX. I haven't tried this, but I hear its great for performance and
usability. It is very flexible on mapping XML to Java using a mapping file
to "meet in the middle". It scores very highly on bindmark:
https://bindmark.dev.java.net/. At this point you cannot just run WSDL2Java,
because that requires some mapping files. I believe there is a tool to
generate these from WSDL but its a manual process at this point I think.
JaxMe. I haven't tried this, but because JAXB2.0 support is almost ready I
wouldn't get into JAXB1.0 at this point.
I hope this helps as a starting point.
Paul
On 12/4/06, kumar.vinodh@wipro.com <ku...@wipro.com> wrote:
>
>
> Hi *,
>
> Axis supports four flavours of databinding
>
> ADB,
> XMLBeans
> Jibx
> jaxme
>
> Is there any document explaining about these data bindings. On what basis
> one should choose the Data binding for the webservice.
>
> Has anyone has come across the document detailing the bindings, its
> advantage, disadvantage.
>
>
> Thanks in advance for your help.
>
> _________________________________________________
> Thanks & Regards,
> Vinodh
>
>
>
> The information contained in this electronic message and any attachments
> to this message are intended for the exclusive use of the addressee(s) and
> may contain proprietary, confidential or privileged information. If you are
> not the intended recipient, you should not disseminate, distribute or copy
> this e-mail. Please notify the sender immediately and destroy all copies of
> this message and any attachments.
>
> WARNING: Computer viruses can be transmitted via email. The recipient
> should check this email and any attachments for the presence of viruses. The
> company accepts no liability for any damage caused by any virus transmitted
> by this email.
>
> www.wipro.com
>
--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
http://bloglines.com/blog/paulfremantle
paul@wso2.com
"Oxygenating the Web Service Platform", www.wso2.com