Index. Spring Web Services 2.0: Best Java Stack for SOAP-based Web Services. A major version of the Spring Web service project Spring WS 2.0 recently was released after a year in development. This version requires that your project use Java 5 or above and Spring 3.0 or above, but the upgrade (if necessary) is well worth it because Spring WS 2.0 delivers a lot of goodies for Java developers. New features include: An improved, more flexible @Endpoint programming modelA new integration testing framework for both server-side and client-side testingJava 5 APIs (generics, varargs), and more For developers who are not familiar with Spring WS, it is a Spring portfolio project that lets you build Spring-based, document-oriented SOAP Web services.
Spring WS is very different from other Java SOAP stacks as it is supports only the contract first Web service development style, it focuses on XML messages, and it does no code generation (except for dynamic generation of WSDL from XSD). I have been experimenting with Spring WS 2.0 during the past several days .
Page 1 of 2. Spring WS 2.0: New Integration Test Support. Spring WS 2.0 introduced a new integration testing module, spring-ws-test, which provides a fluent API for testing both the client- and server-side of Web service. In my previous article on Spring WS 2.0 and SOAP-based Web services , I explored some of the new features introduced in the 2.0 release. In this installment, I'll dive into spring-ws-test. In the previous article, we exposed a SOAP Web service endpoint (using @Endpoint annotation) on the server, but we did not write the client side.
The client side can be written using Spring WS, but it is not mandatory as you can generate client-side code from WSDL using any other framework such as Axis. Spring WS provides a lightweight alternative that does not need a WSDL contract to work. Spring WS provides a class called WebServiceTemplate that developers can use to perform common operations. In this article, I use JAXB2 for marshalling and unmarhalling. Import java.math.BigInteger; public class Client { <? Page 1 of 2. Blitz JavaSpaces. Apache Camel. Apache Camel is a rule-based routing and mediation engine that provides a Java object-based implementation of the Enterprise Integration Patterns using an API (or declarative Java Domain Specific Language) to configure routing and mediation rules. The domain-specific language means that Apache Camel can support type-safe smart completion of routing rules in an integrated development environment using regular Java code without large amounts of XML configuration files, though XML configuration inside Spring is also supported.
Camel is often used with Apache ServiceMix, Apache ActiveMQ and Apache CXF in service-oriented architecture infrastructure projects. Tooling[edit] See also[edit] Books[edit] External links[edit] Apache Tiles 2 - Home. Architecture - Terracotta Developer Documentation - Terracotta. Concursive Corporation.