In this presentation, recorded at the No Fluff Just Stuff Symposium, Scott Davis provides a pragmatic, down-to-earth introduction to Web services as used in the real world by public sites, including SOAP-based, REST and POX-style examples. While the buzzword density leaves nothing to be desired, the presentation contains a very accessible introduction to the core Web services standards.
In this InfoQ interview, recorded at QCon London, Jim Webber, ThoughtWorks SOA practice leader talks to Stefan Tilkov about Guerilla SOA, a lightweight approach to SOA that does not rely on big middleware products, a message-oriented architectural style called MEST and its differences to REST, and the SOAP Service Description Language (SSDL).
The W3C published last month an update to its "Guide to Versioning XML Languages Using new XML Schema 1.1 features" which details the new features of XML Schema 1.1 in the context of schema versioning. They represent real advances for web service practitioners and should become part of your guidelines and best practices when the W3C releases XML Schema 1.1.
WSDL 2.0 has finally been approved as an official World Wide Web Consortium (W3C) recommendation on June 27 2007. The Web Services Description Working Group has been working on the standards for more than 6 years. The recommendation was due on the 31st of December 2006 but has received an extension to the 30th of June this year.
Following up on the debate of REST vs. WS-* discussed here last week, it is interesting to note a debate about "contracts" for RESTful services that has been picking up pace over the last few days.
enunciate 1.0, a J2EE web service deployment framework that provides a complete development-to-deployment system for creating SOAP, REST, and JSON endpoints, was released last week. enunciate is not a web service stack like Axis2 or XFire. Rather, it uses XFire and Spring to provide a code-first development model (not in itself novel) that enforces compatibility contracts at compile time.
Many REST API description languages exist but none have seen major uptake; recently WADL has been getting more attention. Yahoo!'s Mark Nottingham is maintaining a stylesheet to generate docs from WADL. Google's Thomas Steiner unveiled plans for a Google project for generating language specific clients from WADL, & generateing WADL from documentation. Sun is adding WADL tools to SDWP.
WSDL has always been one of the key components on which Web Services have been built. The WS-Addressing working group has had trouble getting enough implementations within the technical committee to ratify their own proposed work with WSDL 2.0. How important is this delay to the take-up of WSDL 2.0? Is WSDL 2.0 right for the industry anyway?
Pete Lacey, author of the "S stands for Simple" dialogue talks to InfoQ about the problems he sees with Web services in general, and SOAP, WSDL and UDDI in particular.
In a short article, Mark Baker claims the default approach to SOA development fails to properly separate concerns, and describes how this is different in Web architecture.
With a very funny blog post that takes a critical look at the history of SOAP, written in the form of a dialogue between a Web services expert and a hypothetical developer, Pete Lacey has started an amazing chain of postings.
XFire, the high performance Java SOAP framework from Codehaus has released version 1.2, the last version before the project merges with Celtix into Apache CeltiXfire. XFire includes such features as Spring integration, JBI support, and pluggable bindings for POJOs, JAXB, and XMLBeans. Improvements since version 1.1 include JiBX data binding, Aegis binding inheritance, and HTTP GZIP.
InfoQ's Stefan Tilkov talks to REST evangelist Mark Baker about REST principles, its benefits, and the relationship to Web services.
WS-MetadataExchange, the Web service standard that specifies how information about a service's interface, policy, and other metadata can be retrieved at runtime, has been updated to version 1.1.
Sun Microsystems has launched the open source initiative called Project Tango. Windows Communications Foundation Engineers are working together with Java Web Services Engineers on the interoperability of enterprise features.