BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage WS Standards Content on InfoQ

  • W3C Workshop on Web of Services Report

    The W3C has released a report about the results of the Workshop on the Web of Services for Enterprise Computing, which was held in February.

  • Is REST Winning?

    The topic of REST as an alternative for integration has been debated on InfoQ many times before. Recent news suggest REST is now gaining mind share among analysts and vendors, with some seeing REST as "the next big thing".

  • The Future of SCA

    In a panel on the Service Component Architecture (SCA) at JavaOne, one of the controversive topics was the SCA client programming model. Moderator David Chappell and Gregor Hohpe share their impressions.

  • Article: Making Sense of all these Crazy Web Service Standards

    Michele Leroux Bustamante explains the most relevant WS-* standards used today in terms of their actual implementation among WS platforms (with a focus on Java and .NET), their level of adoption and readiness. If you are new to web services or to the WS* protocols, or you are having difficulty keeping up with the pace of change in this area, this article should help.

  • Navigating WS-*

    Dan Diephouse has posted a paper, titled "Navigating WS-*", that provides an excellent overview of Web services standards and their respective relevance for solving real-world problems.

  • OASIS WS-RM closes

    The OASIS WS-RM technical committee has closed. This groups work should not be confused with OASIS WS-RX which is still going forward.

  • Sun demonstrates WS-AT interoperability with Microsoft

    Sun's latest Project Tango release includes WS-AtomicTransaction and WS-Coordination support. They also have demonstrated interoperability .NET 3.0 clients.

  • SCA/SDO go to OASIS

    The proprietary SCA and SDO specifications, often seen as competing with JEE and JBI, are taken to OASIS. With Sun now a member, is this a case of happy families?

  • W3C starts two new technical committees

    The W3C announces the start of a working group on Internationalization and one on a Protocol for Web Description Resources (POWDER).

  • WS Reliable Messaging, Policy Updated for Public Review, WS-MakeConnection Introduced

    OASIS has released WS Reliable Messaging, WSRM Policy and a new specification, WS-MakeConnection, for public review. Comments are due until 27 February.

  • WebLogic Server 10 Update: Java EE 5, Spring Pitchfork, WS-*

    BEA has released a new tech preview of WebLogic Server 10 that passes the Java EE 5 CTS. WebLogic Server 10 uses the Kodo JPA (based on Apache OpenJPA)and also Spring's Pitchfork project to provide EJB and Java EE 5. WebLogic Server 10 adds side-by-side deployment of multi-version apps, JMS automatic failover, support for document-centric ws-standards, filtering class loaders, and more.

  • Workshop on Web of Services for Enterprise Computing

    The Workshop on Web of Services for Enterprise Computing, organized by the World Wide Web Consortium (W3C), has led to a number of interesting submissions addressing Web Services and the Web.

  • OASIS WS-Transaction (almost) a standard

    The OASIS WS-TX technical committee held a face-to-face meeting last week at IBM Hursely. This is likely the last such meeting prior to final standardisation of WS-Coordination, WS-AtomicTransaction and WS-BusinessActivity.

  • SOA 2.0 Dead on Arrival?

    Back around JavaOne 2006 Gartner coined the term SOA 2.0 as a new architectural approach, which was superior to "classic" SOA, and Oracle quickly took this and ran with it. There was a lot of backlash from the community, even resulting in the creation of an online petition. Whether or not as a result, SOA 2.0 hype seemed to die off and now Wikipedia has joined the debate.

  • WS-MTOM Policy submitted to W3C

    MTOM has quickly become an important component within the Web Services developers arsenal, offering the composability of base64 with the transport efficiency of SOAP with attachments. But unfortunately it wasn't tied into the rest of the Web Services architecture: there was no standard way for services to advertise that they were "MTOM ready". Until today that is.

BT