The term "Service-Oriented Architecture" is very popular these days, but what does it mean exactly? Is SOA just an abbreviation for Same Old Architecture? And if it isn't, where does the old architecture fit in? In this session, we will cut through the SOA hype and get right to the substance.
In this session, we will talk about SOA's and Web services in a pragmatic fashion. We will talk about the proper place of a Web service within an application architecture, both from the client and the server perspective. And we will talk about the value of SOAP vs REST, and the multitude of WS-* specifications that are out there: what value do they add?
In this presentation Arjen will show you how to implement a contract-first web service using Spring Web Services (WS). If you want to see how to implement standard, public, interoperable web services in Java "the right way" don't miss this session.
Web services experts agree that "contract-first" development is a best practice. That means starting with the public message contract before jumping right into Java code.
Traditionally, however, this best practice hasn't been followed in practice. One possible explanation are the cookie cutter tools that push developers towards a model where methods are exposed in a RPC-like fashion, instead of a document-central model where the public message contract is king.
In this presentation Arjen will show you how to implement a contract-first web service using Spring Web Services (WS), a product from the Spring community that simplifies the development of document-driven web services. We will start with the XML messages that are sent across the wire and create a schema and WSDL around that. Then we implement this contract using both SOAP and REST, showing that the difference is only a matter of configuration. Finally, we will create a client that consumes the Web service.
If you want to see how to implement standard, public, interoperable web services in Java "the right way" this session is for you.