Sun's participation in Web Services Addressing 1.0 - Metadata Interop Testing
The Web Services Addressing Working Group has requested to transition the second Last Call Working Draft of Web Services Addressing 1.0 - Metadata ( which addressed the issues received during the previous Last Call phase relating WS-Policy assertions from WS-Policy wokring group). Section 2.1 Referencing WSDL Metadata from an EPR and section 2.2 Embedding WSDL Metadata in an EPR are marked as risk requiring two interoperable implementations for those features. All the features in the specification except the sections marked at risk were tested for interoperability previuosly.
I am pleased to participate in the interop testing of section 2.1 in Metadata Specification with IBM. The test plan for this feature has been approved by the WG in the last call. Though Sun's implementation of WS Addressing does n't support complete Metadata specification now, it has partial implementation to support EPR's conforming to Metadata specification. Sun has passed all the mandatory as well as optional tests related to this feature. I was pleased to work with David Illsley from IBM in the interop testing from Sun's side. Hopefuly these results will be approved by the WG and then section 2.1 will stay during the transtion from CR to PR phase.
A brief look at how this feature can be helpful when using EPRs to reference Web Services. In JAX-WS you can create proxy from an EPR if the runtime can get all the binding related information from the EPR. This enables the EndpointReference.getPort(SEI) API in JAX-WS to work, as it can get the wsdl metadata from EPR, which can be really useful when dealing with Stateful Web Services feature utilizing addressing headers and EPRS in the background.
If these results are approved by the WSA WG, Section 2.1 is going to stay in PR. Though the plans for full support for WS Addressing Metadata in JAX-WS RI are not concrete yet, this will be available in the near future. I will explain how to reference wsdl metadata in an EPR in a follow up blog.