Basically, the version of JAX-WS included in Java SE 7 is the 2.2 specification. Some new features are listed on the following link: http://jax-ws.java.net/nonav/2.2.6-2/docs/ch02.html
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 specSupport for @XmlElement on SEI's wrapper parameterSupport for @XmlType on exception classesImplement HTTP SPImplement Endpoint API with featuresGenerate new constructors in the generated Service class(service level features, wsdllocation) *Add support for customizing wrapper wsdl:part names as defined in 2.2Add support for customizing wsdl:message name using @WebFault as defined in 2.2Fault customization should accept fully qualified name of the exception class to be generatedCustomization of Service should accept fully qualified class nameAdd Xnocompile option for wsgen similar to wsimportXPath expressions in jax-ws customization can now select multiple nodesDisable server-side exception stacktrace for service specific exceptionsOptimzation of LogicalMessage implementationwsimport 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...