Skip to main content

JAX-WS RI 2.2 Status

Posted by ramapulavarthi on February 26, 2009 at 2:34 PM PST

Its been a long time I blogged. You might be wondering what we are up to with JAX-WS RI lately. We are busy implementing the JAX-WS 2.2 RI.

Jitu, Spec lead for JSR 224 has already sent the proposals on JAX-WS 2.2 features. 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. Since JDK 6 already has JAX-WS 2.1 API, there are some possible classloading issues if you are using JAX-WS 2.2 on JDK 6.
You have to resort to endorsed mechanism or use JDK 5 for now. We are working on alleviating this problem going forward.

I am going to write in detail about the features for WS-Addressing and other enhancements in JAX-WS 2.2 in a later blog. The nightlies will be out soon once the 2.2 API are finalized.

Regarding the JAX-WS 2.1 implementation in JDK 6, We are working on syncing up JDK 6 with latest JAX-WS 2.1.X. You should see it in a future JDK 6 feature update release.

Related Topics >>

Comments

JAX-WS RI 2.2-hudson-752

This version is included in the comments when web services are generated using NetBeans 6.8 and from what we can tell it works well. Are JAX-WS libraries which are included with NetBeans 6.8 available anywhere in a maven repository? I asked this question on the NB users group and was told they are the same but I am not convinced this is the case at this time. If one creates a maven project in NetBeans and then uses the wizard to add a web service client it uses an older 2.1 version. We need the newer version to consume Axis2 web services which use multiple namespaces and the JAX-WS which NetBeans uses with native projects seems to handle this. Any help would be appreciated. TIA, Carl

Once the API in in Java SE, it is impossible to remove it. We plan to explore more options to ease the pain of endorsed problems. nillable support works with JAX-WS 2.2 nightlies. See the unit test case http://fisheye5.cenqua.com/browse/jax-ws-sources/jaxws-unit/testcases/fr... I think the Flex problem is that it doesn't understand imports in the WSDL. So we made a note of it to support in 2.2 Collections is a tough problem to solve. But if you could file a bug and what you would expect us to do, that would be great.

You guys really do need to resolve the endorsed directory issue once and for all. For this reason I really would like to see JAX-WS removed from JDK 7. IMHO, you need to focus more on basic interop and usability also instead of seemingly only focusing on more advanced standards. i.e. Will nillable web method parameters be supported? I would also like to see hash table support that works with Silverlight/WCF and Flex clients. Furthermore, it would be nice if you could do something to make WCF recognize collections as lists rather than just arrays. I still don't understand why JAXB serializes collections in such an odd manner either. If you would focus on getting this stuff to work well with other systems such as Flex (as broken as their web service support is), it would help developers of real-world apps greatly.

Hi syvalta, The support for schema validation is not introduced in JAX-WS 2.2 API. Its support would require the definition of how schema should be in rpc/lit case. 2.2 spec did n't define anything in particular for timeout parameters. JAX-WS 2.2 spec is providing a way for passing instances of WebServiceFeature during the Service instance creation. In RI we are planning to use that WebServiceFeature mechanism to support Timeout parameters etc. I agree that this will be RI specific

Hi Rama, will JAX-WS 2.2 API (or is it JSR 181actually) support schema validation? I know Sun implementation has supported it for some time already, but will the support be included in the API? How about support for setting transport timeout parameters in a provider independent way, will that be included in the API?

Hi Kristoff, Its should be available in a week or two and would be available in Metro 2.0 nightlies then.

Is 2.2 going to suppor @XmlElement on fields in wrapper style as hinted at on the one-pager? If so, when can we expect to see that in the Metro 2.0 nightlies?