http://www.soamag.com The SOA Magazine is a monthly online publication provided by SOA Systems Inc. and Prentice Hall/PearsonPTR and is officially associated with the "Prentice Hall Service-Oriented Computing Series from Thomas Erl." SOA en-us Copyright 2006-2010, SOA Systems Inc. http://www.soamag.com/I37/0310-3.php In Part 1 of this article series, I had used the popular Spring framework, a lightweight container that provides automated configuration and wiring of application objects, to create a contract-first Web service. Demonstrating Spring's pluggable architecture, we had seen how to configure the endpoint with Spring's support for OXM (Object-XML Mapping) and handle service-level and runtime exceptions. In this article we'll go over the security configuration using Spring's support for WS-Security providing message-level authentication, and optionally message confidentiality and message integrity services, ORM (Object-Relational Mapping) to deal with persistence at the object level, and DAO for data access to a relational database storing user-credential information. Next, we'll look at how Spring automatically generates the WSDL document using the data contract created earlier and, lastly, the client configuration required to invoke and consume the Web service... SOA http://www.soamag.com/I37/0310-3.php#When:30.07.09 http://www.soamag.com/I36/0210-2.php In this two-part article series, I'll be demonstrating a service-oriented solution architected and configured using Spring, a lightweight, open-source framework that is specifically created to provide a one-stop shop for all your enterprise application development needs using plain JavaBeans. Specific sections will address core architectural concerns such as the Web service infrastructure (specifically as it relates to endpoint setup, message definition, (un)marshalling, and routing), exceptions handling, security infrastructure and the client setup. Demonstrating Spring's modular and pluggable architecture, we start with Spring-WS, the specific Spring module created for Web services and plug-in other Spring modules such as OXM (Object-XML Mapping) specifically to address the Object/XML impedance mismatch, Security for authentication/authorization services... SOA http://www.soamag.com/I36/0210-2.php#When:30.07.09 http://www.soamag.com/I30/0709-3.asp JBossWS is a framework which implements the JAX-WS 2.0 (a replacement for the earlier JAX-RPC) specification and defines the programming/runtime model for implementing web services as a remoting mechanism for distributed service-oriented architectures. JBossWS is targeted at the Java SE 6/EE 5 platform and integrates with most current and earlier JBoss Application Server releases. In this article, We demonstrate how easy it is to use the JBossWS framework to harness the power of Java 5 annotations as well as endpoint associated metadata provided by JSR 181 annotations to develop, provide, consume and secure a service. The annotations ensure that the source code will be fairly simple and straightforward POJOs with the onus of processing falling to JBossWS tools at the client and server to create the contract and infrastructure plumbing needed at deployment and runtime. In order to illustrate the concepts, We will use the example of a real life service that allows different systems within our organization (a State Government Agency) to integrate with a centralized Forms system to retrieve, deliver and process intelligent documents to and from end users. SOA http://www.soamag.com/I30/0709-3.asp#When:30.07.09 http://www.soamag.com/I31/0809-2.asp With the exponential growth of the Web, REST as an architectural style has found its niche in the modern services landscape with its popularity poised to grow even further. JAX-RS is a new JCP specification that provides a Java API for RESTful Web services over the HTTP protocol. JAX-RS uses annotations on POJOs (Plain Old Java Objects) to map to the RESTful architectural style of presentation and facilitates lookup of distributed enterprise resources via Uniform Resource Identifiers (URIs). In this article I demonstrate a RESTful service-oriented architecture created to wrapper similar functionality as detailed in to enable a client application render an Adobe form and process form submissions abstracted away into Adobe Form Server Module (FSM) factory objects. Corollary to Service Endpoint implementations in JAX-WS, here we have JAX-RS annotated Web Resource classes (the RESTful term for a service) instantiated per each HTTP request that encapsulate the service functionality and Providers that transform the resource parameters and result content into runtime representations in a variety of media types... SOA http://www.soamag.com/I31/0809-2.asp#When:31.08.09