InfoQ

InfoQ

InfoQ

En | 中文 | 日本語 | Br

562,907 Jan unique visitors

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

WS-Addressing Becomes a W3C Recommendation

Posted by Stefan Tilkov on May 11, 2006

Sections
Enterprise Architecture
Topics
SOA ,
WS Standards
Tags
SOAP ,
WS-Addressing
The WS-Addressing core specification and the WS-Addressing binding to the SOAP protocol have reached full Recommendation status at W3C, turning them into what is commonly referred to as "W3C standards".

The WS-Addressing core specification describes the abstract properties to encode addressing information independently from the underlying transport protocol; the SOAP binding maps these to the SOAP 1.1 and 1.2 protocols. The WS-Addressing binding to WSDL is still at last call working draft status.

WS-Addressing, originally developed by Microsoft, IBM and BEA, had been submitted to W3C in August 2004 after a competing specification by Sun, Oracle, IONA and others, the now irrelevant WS-MessageDelivery, had been submitted in April. WS-Addressing is referenced by many other specifications such as WS-ReliableMessaging (currently being standardized at OASIS) and WS-Eventing (recently submitted to W3C).
  • This article is part of a featured topic series on SOA

1 comment

Watch Thread Reply

JSR-261 by John Harby Posted

  1. Back to top

    JSR-261

    by John Harby

    In following, JSR 261: JavaTM API for XML Web Services Addressing (JAX-WSA) has posted a second early draft for review. See:
    jcp.org/aboutJava/communityprocess/edr/jsr261/i...

    Reply

Educational Content

Jesper Boeg on Priming Kanban

In this interview, Jesper Boeg, author of the new InfoQ book – Priming Kanban, discusses the keys to using Kanban effectively, and how to get started if you are currently using other approaches.

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.