One of the principal problems with normal WCF development is code reuse. No matter how well you design your classes on the server, once the proxy generator has touched them you get nothing but simple DTOs. This article shows how to bypass the proxy generator so that your client and server can share code.
Heshan Suriyaarachchi covers some of the key concepts of the Apache Axis2 Web Service engine and how it can be extended to support JVM based scripting languages such as Jython, Jruby, etc allowing them to be used to both expose web services and write web service clients.
SOAP and REST both work, and both have pros and cons around interfacing to web services. But, it is up to the web developer to make the decision of which approach may be best for each particular case. 24
Brian Sletten discusses REST architecture, SOAP and WS-*, Semantic Web, URLs as IDs, URIs and URNs, freedom of form, logically-connected late-binding systems, HATEOAS, and the impact of Semantic Web. 19
SOA is 10 years old. InfoQ has gathered Jeff Andres, Eric Ballou, Dave Hollander and William El Kaim, all experienced Enterprise Architects, to share their perspectives as part of a virtual panel. 3
Thin client paradigm characterized by web applications is a kludge that needs to be repudiated. Old compromises are no longer needed and it's time to move the presentation tier to where it belongs. 24
InfoQ is pleased to provide a hosted chapter from the recently published "Essential Windows Communication Foundation" authored by Steve Resnick, Richard Crane, and Chris Bowen.
InfoQ spoke to the lead developers of the most important open source Java Web-services stacks about their design goals, standards, data binding, XML, interoperability, REST support, and maturity. 12
Michele Leroux Bustamante explains the most relevant WS-* standards used today, their implementation among WS platforms (with a focus on Java and .NET), level of adoption and readiness. 7
InfoQ had a chance to talk to WS-* expert and WSO2 CEO Sanjiva Weerawarana about Web services standards, Microsoft's role, and the ongoing REST vs. SOAP/WS-* debate. 39
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. 31