services stack from GlassFish
is kicking strong these days - here are two instances!
- ArcGIS SOAP stack gains 90% performance improvement using
in the Web services team for performance enhancement of href="http://resources.esri.com/help/9.3/arcgisserver/apis/soap/index.htm">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
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 href="http://rahulswackyworld.blogspot.com/2008/07/internship-that-changed-my-perspective.html">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
is current, but has become very large, the doc is poor, the support is
invisible, the generated code smells, and the seams are
Fifty nine jar files? Really? Do I need
this hassle? With JAX-WS,
do I need AXIS any longer? I think not."
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 you can also
to Microsoft Exchange Server using JAX-WS.
And here are some
endorsements for Metro.Technorati: href="http://technorati.com/tag/webservices">webservices