Hi Danny, I guess you have already made the choice to pick either CXF or Metro (which is not a bad choice at all). All the three frameworks are good and all have pros and cons (much more than you have listed). However, without knowing your requirements I cannot recommend any of those. All three are good for Web services, but when it comes to specific features one become better over other.
Any service you deploy is automatically exposed as both REST and SOAP (and also both WSDL 1 and 2). We do not use WSDL behind the seen, however we do provide much better way to customize REST binding using WSDL 2.0. I am not going to comment about CXF and Metro, because it is unfair to comment on those in an Axis2 biased list. Deepal > 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 -- Blog - http://blogs.deepal.org/
