By Jiandong Guo on Dec 06, 2008
Metro is a high-performance, extensible, easy-to-use web service stack. It is a part of the GlassFish offerings, but it can be also used outside GlassFish. Metro is also integrated into OpenSSO for an Security Token Service (STS), and OpenESB for SOAP and security handling.
In the past year or so, the adoption of Metro is in surge. Here is a list of some of the endorsements of Metro as in http://blogs.sun.com/stories/:
"JPA (Toplink Essentials) and JAX-WS (Metro) are the key server-side technologies used by Apologic"
"In one particular project we used both OpenESB and Tomcat+Axis2 (on separate machines), where project Metro (WSIT compliance) was a major factor to the success."
"We have done some performance and stability testing and found that response time was quite impressive, better than IIS 6.0. One simple observation, when you first call a Web Service instance running on IIS is a lag lasting a few seconds which. On the terminal side, this lag using GlassFish is almost invisible to users. We were very pleased with the result but also with the monitoring features for Web Services which are really helpful."
4. FAA's NASE
"Setting up JDBC resources, Web Services, and HTTP Services are smooth as a glassfish."
"We decided to use JEE5 based technologies - JSF, JAX-WS and JPA - and the only complete application server which was capable of supporting these technologies at the time was Glassfish."
6. Fraunhofer Gesellschaft
"Yes, we investigated several open source web service frameworks, e.g. Apache Axis 2 and JBoss Web Services. The choice to use WSIT is based on the promoted interoperability with Microsoft platforms."
"The architecture uses GlassFish's Metro to expose a BAPI (SAP's most used API) as a Web Service. As of this writing, the architecture in production relies on the latest and greatest 9.1 ur1 release which integrates Metro 1.1. NetBeans was used as the IDE to develop the entire code in a record time."
"We use Web Services for access to timetables and information about actual traffic from the airport web server."
" We mainly use Web Services (Metro) to communicate with .Net."
"Specifically, Java Persistence (JPA), EJB 3.0, and Web Services API (JAX-WS) are the main new technologies used by Imixs."
11. Microsoft BizTalk
"As a result of this collaboration, Metro 1.2 is going to be a better and more interoperable release for the Sun's customers and the greater Java community and BizTalk Services as well as our future identity products will be better and more interoperable, too. Win-Win. Thank you, Sun."
With more than 10 posts in an average day, Metro forum is one of the most popular one among java.net forums . This is an indication of a large user base for Metro. The interests in Metro as shown up in the forum ranging from low level JAXB API to the most advanced features like WS-Trust based STS. Here is a forum thread where an user is uing Metro WS-Trust support to build Enterprise interoperable health care solution based on
Oasis XSPA (Cross-Enterprise Security and Privacy Authorization) WS-Trust Profile:
"I hate to be a bother on the forums, but we're doing exciting stuff with Metro for a big standards (e.g. OASIS) interoperability demo coming soon. Its great stuff so far."
A Bother? No. Exciting and great stuff? Yes, indeed.