Here is an excerpt that features changed between versions 2.1.7 and 2.2:
Add WS-Addressing 1.0 Metadata support as per 2.2 spec
Support for @XmlElement on SEI's wrapper parameter
Support for @XmlType on exception classes
Implement HTTP SPI
mplement Endpoint API with features
Generate new constructors in the generated Service class(service level features, wsdllocation) *
Add support for customizing wrapper wsdl:part names as defined in 2.2
Add support for customizing wsdl:message name using @WebFault as defined in 2.2
Fault customization should accept fully qualified name of the exception class to be generated
Customization of Service should accept fully qualified class name
Add Xnocompile option for wsgen similar to wsimport
XPath expressions in jax-ws customization can now select multiple nodes
Disable server-side exception stacktrace for service specific exceptions
Optimzation of LogicalMessage implementation
wsimport now handles URL redirection of imported wsdls correctly
* I experienced myself this addition in the javax.xml.ws.Service class (extended by proxy generators created by wsimport). Unless your application classpath is configured in a very specific way, this may force you to stay with JAX-WS 2.0/2.1 if you are using Java SE 6, and go on with JAX-WS 2.2 if you use Java SE 7.
However, I have a few remaining questions that Deepak might answer below...
Joined: Jun 17, 2008
As mentioned above, I have a few other questions:
Apart from migrating to JAX-WS 2.2, which involves the differences I listed above, are there any other significant new features from a Java SE 7 point of view?
How can I tell the exact version of JAX-WS in function of the JDK release? For example, what JAX-WS version is embedded in JDK 1.6.0u32 (2.1.6, 2.1.7, ...)? in JDK 1.7.0u5 (2.2.5, 2.2.6, ...)? and so on...
I think this last question is important due to the fact that — contrary to Xerces, for example — the package names are exactly the same in the JDK and in any JAX-WS distribution found on http://jax-ws.java.net. This is why the classpath question is critical when using JAX-WS 2.2 with JDK 6...