Why GlassFish Metro over Axis ?
By arungupta on Jul 30, 2008
Metro (Web services stack from GlassFish) is kicking strong these days - here are two instances!
- ArcGIS SOAP stack gains 90% performance improvement using
An intern in the Web services team for performance enhancement of ArcGIS SOAP SDK reported:
"With Axis 1.x based tool kits XML parsing was identified as a bottleneck and therefore we wanted to make a switch to a tool kit that uses the Streaming API for XML Parsing (StAX). We identified that Metro (Glassfish's SOAP Stack) was the way to go and i generated the new Metro based SDK for accessing Web-Services."
And the conclusion is ...
"The result of this project is an increased performance of the ArcGIS Server's SOAP stack (by about 90%)."
Pretty cool - Metro (Web services stack baked in GlassFish) gave about 90% improvement over Axis! Read more details about the study here.
of the guard: AXIS out, JAX-WS in
Here are some relevant points:
"I have come to a conclusion: I no longer want to deal with the hassle that has become Apache AXIS."
"AXIS2 is current, but has become very large, the doc is poor, the support is invisible, the generated code smells, and the seams are everywhere. Fifty nine jar files? Really? Do I need this hassle? With JAX-WS, do I need AXIS any longer? I think not."
"But I honestly cannot believe customers will continue to put up with the furball that AXIS2 has become. And if I am in a position to make a recommendation, I will recommend JAX-WS. It works."
And here are some other endorsements for Metro.
Technorati: webservices adoption glassfish metro axis