Hi John,
WSIT is just Sun/Oracle's implementation of WS-Security and related
standards. The WSIT developers did focus on interoperability with .NET,
but I think CXF's implementation is just as interoperable -
interoperability should properly be based on correct implementation of
standards, rather than on testing with one other particular
implementation, and CXF has worked hard in this area.
So I don't think the .NET interoperability should really be a concern
for you in choosing between the two stacks.
- Dennis
Dennis M. Sosnoski
Java SOA and Web Services Consulting <http://www.sosnoski.com/consult.html>
CXF and Web Services Security Training
<http://www.sosnoski.com/training.html>
Web Services Jump-Start <http://www.sosnoski.com/jumpstart.html>
On 07/07/2012 06:17 AM, johngalt wrote:
I was looking for a bit of information from experienced
users of different java web services frameworks.
Specifically: CXF, Metro, axis2
I have an new environment with many different web services: WSDL and REST,
Java and .NET WCF
So I've been trying to go through the specfics of each framework to
determine which is the best
for my environment.
Here is what I've found, based on a few hours of googling.
CXF - PROS - WSDL and REST (implements both JAX-WS and JAX-RS)
- CONS - Doesn't support WSIT for the WSDL side of things, for WCF/Java
interoperability
Axis2 - CONS - REST support for only GET and POST (seems to use wsdl behind
the scenes even for REST?)
Metro - PROS - WSIT support on the wsdl side
- REST support if I include Jersey
So it seems like CXF or Metro is a good choice, depending on how many wsdl
services I think
will be Java/WCF or WCF/Java.
Any input, opinions, past experiences, corrections, etc, appreciated:
Cheers
--
View this message in context:
http://cxf.547215.n5.nabble.com/CXF-Metro-Axis2-tp5710691.html
Sent from the cxf-user mailing list archive at Nabble.com.
