Hi Srini,
Metro has a small performance advantage over CXF and Axis2, though
that's mostly significant for small messages. Generally the performance
with large messages is going to be more of a concern, and there the
three are pretty close (as long as WS-Security isn't involved).
Personally, though, I think Metro is only a good choice if you're buying
into the whole Metro+NetBeans+Glassfish combination. Metro documentation
is mostly based around using NetBeans and Glassfish, and the
configuration is somewhat messy if you're doing it directly.
If you are using WS-Security, CXF seems to have the best all-around
support for WS-Security features while also providing very good performance.
In terms of interoperability, that's largely a function of the XML
schemas you're using, which in turn depends on your data binding. Metro
only supports JAXB data binding, while CXF supports both JAXB and
XMLBeans (with JiBX support in the works). If you're starting from Java
code your best approach to generate a schema and WSDL is to use my
Jibx2Wsdl tool, which cleanly handles most types of Java constructs
(including multi-dimensional arrays). You wouldn't be able to use the
generated JiBX bindings with CXF at present, but you'd be able to use
the generated schema and WSDL to generate code using JAXB.
I do teach in-house training courses on all these issues, including CXF
and Metro usage, so feel free to contact me directly if your
organization could use some help in getting started.
- Dennis
Dennis M. Sosnoski
SOA and Web Services in Java
Training and Consulting
http://www.sosnoski.com - http://www.sosnoski.co.nz
Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117
Srinivasa K wrote:
Hi Dennis,
Thank you very much for the details that you provided. When we
reviewed your article, it seems Metro is good in performance point of
view - compare to CXF and Axis2. Do you suggest to go with Metro? At
this point of time we are looking for the best one in overall
performance and implementation.
We have web services clients with different platform, like Java, C#
and Natural(SotwareAG). We also have to consider the best
interoperability with this platforms. We tested with Axis2 on C#
client and we solved array issues that we had with Axis1.
We appreciate your suggestion on this.
Thanks,
Srini
On Tue, Jun 22, 2010 at 12:15 PM, Dennis Sosnoski <d...@sosnoski.com
<mailto:d...@sosnoski.com>> wrote:
Dennis Sosnoski wrote:
...
My IBM developerWorks series on Java Web Services
(http://www.ibm.com/developerworks/views/java/libraryview.jsp?search_by=java+web+services:)
has details on the configuration issues and performance
(though the main performance article on CXF seems to be
missing in the search results right now - I'll post a direct
link to that when I can track it down).
I saw that Ibrahim had this "missing link" in his email response
(thanks, Ibrahim!):
http://www.ibm.com/developerworks/java/library/j-jws14/index.html
- Dennis
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
<mailto:java-user-unsubscr...@axis.apache.org>
For additional commands, e-mail: java-user-h...@axis.apache.org
<mailto:java-user-h...@axis.apache.org>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org
