News

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

JAX-WS 2.2 and Metro 2.0 Nightly Available

Posted by Dionysios G. Synodinos on Mar 16, 2009

Sections: Enterprise Architecture,; Architecture & Design,; Development
Topics: Java ,; Web Services ,; Languages ,; SOA ,; Enterprise Architecture ,; Programming ,; Architecture ,; WS-Star ,; Interop

Rama Pulavarthi, member of the Java Web Services group at Sun Microsystems, has reported on the availability of the JAX-WS 2.2 and Metro 2.0 nightly builds. JAX-WS 2.2 is mainly aimed to add support for WS-Addressing 1.0 - Metadata specification and Metro 2.0 is scheduled to be delivered on GlassFish v3.

Rama explains about the new features of JAX-WS and the Project Metro Roadmap:

JAX-WS 2.2 is mainly aimed to add the missing support for WS-Addressing 1.0 - Metadata specification in the earlier release. This requires WS-Policy 1.5 support in JAX-WS to understand the WS-Addressing Metadata defined policy assertions. For WS-Policy 1.5 support, JAX-WS is using the Policy implementation from WSIT ( Policy project on java.net). We have integrated the Policy libraries in JAX-WS 2.2 and with this JAX-WS can understand/generate policies as defined in Web Services Policy 1.5 -Attachment.

JAX-WS 2.2 will be part of Metro 2.0. The roadmap for Metro 2.0 can be found here and more details on the features targeted for Metro 2.0 are on Metro One Pagers. Some of the support for WS-Addressing Metadata is already implemented. The development for JAX-WS 2.2 is happening on jaxws22 branch of jax-ws-sources/jaxws-ri repository.

JAX-W 2.2 nightly builds are available as well as the Metro 2.0 nightly builds which include JAX-WS 2.2 and JAXB 2.2.

Developers that will try to take the new libraries for a test-drive must be aware that the Metro 2.0 contains JAX-WS 2.2, which clashes with the JAX-WS 2.1 that comes with Java SE 6:

We have recently had reports in the Metro user forum where people that ran Metro 2.0 with Java SE 6 had trouble using wsimport.

For a detailed analysis when exactly this is happening, see this Wiki page. The reason for these failures is that Metro 2.0 contains JAX-WS 2.2, which clashes with JAX-WS 2.1 ¹ that is built into Java SE 6. You will only see these failures if you did not install Metro 2.0 with our installation scripts metro-on-glassfish.xml/metro-on-tomcat.xml. That is the case if you e.g. installed Metro 2.0 for GlassFish V3 via the update center or if you use a version of GlassFish V3 built into NetBeans.

The simplest solution is to download the Metro 2.0 nightly build and run the installation script. The script copies the file webservices-api.jar, which contains the JAX-WS 2.2 API, into <java-home>/lib/endorsed. Alternatively, you can of course manually copy webservices-api.jar into a suitable endorsed directory.

The reader can find more information on Project Metro on the Metro wiki and the “One Pagers”.

Dionysios G. Synodinos is a Web Engineer and a freelance consultant, focusing on Web technologies