Posted by kohlert
on August 30, 2006 at 2:25 PM PDT
With the announcement of JAX-WS 2.1 MR, it is apparent that versioning JAX-WS web service is important.
With the announcement of JAX-WS 2.1 MR, it is apparent that versioning JAX-WS web service is important. As the 2.1 MR will add additional functionality and will potentialy introduce new annotations, it will become imperative that JAX-WS tools allow the web service developer to specify the target version of JAX-WS. The JAX-WS RI for example, will add targetVersion options to wsimport to control what code will be generated. The default value will be JAX-WS 2.1, but if the web service developer wants to target 2.0, he will be able to specify -targetVersion 2.0 to the wsimport command. By specifying the -targetVerion 2.0 option, then the generated code will run on a JAX-WS 2.0 implementations. Without specifying this option, 2.1 annotations might be generated making it impossible to run the application on a 2.0 implementation.
The question I would like to ask the community, is there a desire for a standard way to specify the targetVersion? For example, a customization could be defined for targetVersion. This would allow web service developers to specify this options in a standard way that would work across JAX-WS implementations.
Technorati: JSR JCP JAX JAXWS Web Services