SOA Tips | Page 34


  • Finding the ROI in SOA

    As anyone who has worked with SOAs and Web services can attest, it can be tough to know ahead of time what return on investment (ROI) a project can return. This column offers advice on where to loo...

  • ZapThink's 2005 SOA Scorecard and 2006 Predictions

    The traditional end-of-year ZapFlash focuses on revisiting our predictions and analyses over the past year and speculating the future of SOA and Web Services.

  • An emerging XML Web services security infrastructure

    On the Internet everybody shares the same security problems. This XML tip discusses how the W3C and OASIS are working to change that.

  • WSRF: Accessing stateful resources with Web services

    This tip discusses how WSRF is a specification designed to deal with stateful resources in the context of Web services.

  • Is that XML valid?

    The purpose of this tip is to discuss various levels of XML "validity" and the tools in the Java 1.5 standard edition that can be used to check XML documents.

  • Security in .NET 2.0

    The new security components in .NET 2.0 can help you greatly reduce the amount of code you need to write in order to make your applications secure.

  • SOA for Value Chains

    This tip discusses the value chain, from the suppliers of components to the assembly of those components into finished goods to the end customer is a complex web of interactions.

  • Using Altova's XMLSpy 2006 Visual Studio .NET Integrati

    This article discusses the features of the XMLSpy 2006, a widely-used XML development environment.

  • WS-Inspection: Discovering Web services

    This article discusses WS-Inspection, a service discovery mechanism used for Web services.

  • The Subtleties of Service Convergence ZapFlash

    This ZapFlash discusses the meanings for the term "software service" and why there is a convergence taking place in the marketplace among the various types of software services.

  • The Java XML Digital Signature API Spec (JSR 105)

    This tip discusses how Java XML Digital Signature API (JSR 105) Version 1.0 makes standard programming interface available to Java that complies with a variety of related W3C recommendations.

  • REST: Simplicity in Web Services design

    In this tip, an alternate approach to deploying a Web services compliant architecture named Representational State Transfer (REST) is discussed.

  • How To Overcome Ajax Roadblocks

    In this second part of a two-part column we'll look at roadblocks to wider Ajax deployment for Web services and SOAs -- and what it will take to overcome them.

  • BPEL: Web Services orchestration, hands-on with ActiveB

    Once the initial design of SOA is done, coordinating individual services in an aggregated manner implies another set of requirements, most of which can be addressed through BPEL.

  • Right-sizing services

    Early proponents of SOA realize they must size their services just so and tackle aspects of architectural best practices. This tip discusses how SOA requires correct implementation.

  • Alternatives to JAXP

    This follow-up tip discusses two popular alternatives to JAXP and why some Java programmers prefer them.

  • Why Ajax may be the future of Web services

    Ajax, a programming technique for creating rich, Web-based applications that look and work like desktop software, has become increasingly popular on the Web, on sites built by Google and others. Th...

  • What to look for in a SOA maturity model

    In this ZapFlash, Jason Bloomberg gives advice on how to understand what the differences are among the various SOA maturity models.

  • A look inside the Java API for XML Processing

    Beginning with Java 1.4, XML processing tasks can be handled with the classes in the standard edition. This tip discusses the built-in XML capabilities of Java 1.5.

  • Remaking the Java ESB: JBI and ServiceMix

    In this article, Daniel Rubio explores the concepts behind JBI and an open source implementation named ServiceMix.