Today there is no shortage of articles, case studies, and analyst research concerning service oriented architecture (SOA), discussing the benefits of exposing existing IT capabilities as services and reusing these services to create composite applications. However, in their articulation, they are missing how these benefits will be useful to the ultimate end user, i.e. business analysts. Since SOA projects are all about business and IT alignments, support from these business end users is a key to successful SOA adoption efforts in any enterprise. Many SOA projects fail when IT doesn't look at the business side of an SOA solution and business doesn't see SOA as important.

The Service Modeling Language (SML) Working Group released the First Public Working Drafts of the Service Modeling Language, Version 1.1 and its Interchange Format. SML is used to model complex services and systems including their structure, constraints, policies and best practices. Based on XML Schema and Schematron, SML allows inter-document references and user-defined constraints.

The Glassfish Wiki has a new FAQ posted, with the subject title "What are the differences between Server and Client side state saving and what are the benefits/drawbacks of each?" Both are easy to use, being a simple parameter in web.xml, but the implications of them aren't always clear. This FAQ tries to summarize the two methods.

This article provides an overview of Project Tango, an open source implementation from Sun Microsystems of the key enterprise Web services specifications, commonly known as WS-*, that provides interoperability with .NET 3.0.