For a starting project, why would you use Metro instead of Axis2?
What should be considred? Performace? Easiness? Tools/IDE/Plugins availability?
A:
I wouldn't use metro, I would go either with Axis2 or with CXF (ex XFire).
Dev er dev
2009-02-06 08:47:22
why?what are you considering?
Lucas -luky- N.
2009-02-06 09:27:17
For me, the ability to use the same servce interfaces on both server and client side is the main reason.
Dev er dev
2009-02-06 09:42:07
Are SOAP web services so non-interoperable that you need the same stack on both client and server? That would be a substantial reason to abandon SOAP if it were true.
Jim Ferrans
2009-05-19 01:57:56
Not so, but slightly incompatible here and there, and that will eventually bite you sooner rather then later.
Dev er dev
2009-05-19 08:20:59
@Dev er dev, which incompatabilities do you have experience with? Might save others running into the same issues.
Thorbjørn Ravn Andersen
2010-02-19 13:07:12
+7
A:
I have used Axis, CXF and JAX-WS (Metro). To me Axis just feels so, out of date and wrong in many ways, so I wouldn't use that. If your application is using Spring then Apache CXF is clearly the stack you should be using. If on the other hand, you don't use Spring, then JAX-WS is they way forward. The good thing about JAX-WS is that it is included with the Java 6 runtime, thus easy to install. :)
For tools, IDE and plugins, I've been using Maven quite extensively and plugins exist for all of those WS stacks mentioned.
Guðmundur Bjarni
2009-02-06 09:15:24