This article, based on a chapter from the book "Service Oriented Architecture Demystified", discusses the benefits of applying SOA to heterogenous environments in the healthcare domain. Focusing on a domain instead of technology perspective first provides an interesting view on the business motivation for SOA.
InfoQ's Stefan Tilkov questioned lead developers of Apache Axis2, Apache CXF, Spring Web Services, JBossWS and and Sun’s Metro about their design goals, their approach towards Java and Web services standards, data binding, accessing XML, interoperability, REST support, and framework maturity. The results revealed many similarities and some noteworthy differences.
There are many occasions where software creates XML output: XML documents are used for data interchange between different applications, web application create (X)HTML output or respond to AJAX requests with XML, and this has to be tested as much as anything else. In this article, Stefan Bodewig explains how to perform those tests with the XMLUnit framework he has co-authored.
Ted Neward demonstrates how Office 2007 files can be read and written without anything more complicated than the native JDK itself. 25
InfoQ had a chance to talk to Frank Cohen about his FastSOA methodology and architectural patterns. We have also published a one-chapter excerpt from his book on the topic. 6
Rails makes it easy to support micro-format standards alongside XML in RESTful applications, potentially opening them up to a wider audience and/or reducing their bandwidth requirements. 1
In this article, Stefan Tilkov proposes 10 principles to serve as a basis for SOA discussions, focusing on abstract concepts that are independent from any particular vendor framework. 6
Spring Web Services creator Arjen Poutsma talks about Spring's WS stack and the different approach it has to building Java Web services. 7
.NET and Java interop can be made really simple using a REST document centric approach. This article demonstrates REST for interop as well as POST-REST. 4