InfoQ

News

Sun Announces Metro

Posted by Mark Little on Jun 20, 2007

Community
SOA
Topics
Java plus .NET Integration ,
Web Services
Tags
Sun Microsystems
With interest continuing to grow in Sun's Project Tango and JAX-WS support from other vendors also on the rise, Sun has decided to give a new name to the combination of the JAX-WS Reference Implementation and Project Tango: Project Metro. According to the Arun Gupta:
JAX-WS, the core platform, uses Tube as a basic processing unit that represents SOAP-level protocol handling code such as MustUnderstand and WS-Addressing processing. Multiple tubes are put together in a sequential fashion to complete the SOAP message handling. Project Tango uses this extensible architecture to implement they key WS-* specs, such as Reliable Messaging and Atomic Transactions, as Tubes as well.
Because underground railway systems, aka rapid transits, use tubes and are often referred to as metro's, you have the name! (Naming software projects is not easy, as this attempt shows!) But why a new project? Sun's Harold Carr believes there's been a lot of confusion around Project Tango and the JAX-WS RI:
... some people think that Tango is a different stack than our JAX-WS RI stack. But that is not the case. Tango is implemented on top of the JAX-WS RI. So, sometimes, to make this point in email messages, we've been saying "JAX-WS RI + Tango".
Plus the fact that Reference Implementation can be taken by some as meaning not a product, when in fact that is not the case. So Metro it is. Although at this point documentation, web sites etc. will continue to refer to the old names and the Metro binary is the Tango binary, including the JAX-WS RI.

No comments

Watch Thread Reply

Educational Content

Brian Marick on 4 Challenges and 5 Guiding Values of Agile Software Development

Brian Marick takes us through a quick tour of the most important values and challenges to adopting Agile successfully (they aren't the typical challenges and values we hear in the community).

Are You a Software Architect?

The line between development and architecture is tricky. Does it exist at all? Is an ivory tower actually needed? There's a balance in the middle, but how do you move from developer to architect?

Agile – A Way of Life and Pragmatic Use of Authority

The word 'authority' sometimes produces an allergic response in hard-line agilists. Freedom and authority – both are bad if misused and both are good if used in right spirit for a noble cause.

Getting Started with Grails, Second Edition

"Getting Started with Grails" brings you up to speed on this modern web framework. Companies as varied as LinkedIn, Wired, and Taco Bell are all using Grails. Are you ready to get started as well?

Using ITIL V3 as a Foundation for SOA Governance

Those familiar with only ITIL V2 often scoff at the thought that ITIL could serve as a governance framework for SOA. With ITIL V3, the focus of the framework shifted towards service-orientation.

Adrian Colyer on AspectJ, tc Server and dm Server

SpringSource CTO Adrian Colyer discusses AspectJ, SpringSource's dm Server and tc Server products, OSGi and Scrum.

Adam Wiggins on Heroku

Heroku's Adam Wiggins talks about Rails, Background Jobs, Add-Ons, Ruby, and how Heroku manages to work around Ruby's inefficiencies using Erlang and other languages.

SOA as an Architectural Pattern: Best Practices in Software Architecture

For Grady Booch the foundation of a good architecture is patterns, SOA being just one of many patterns. In this Second Life presentation, Booch attempts to bring more clarity on what architecture is.