We should also somehow handle new "-target" option of wsimport when upgrading to
new JAX-WS version, IMHO.

From the mail from Vivek P. to users@jax-ws:
"...
    * Improved wsimport
          o -quiet switch
                + wsimport works in silent mode
          o -target switch
                + wsimport generates code as per target spec version. It
                  preserves the source level compatibility with
                  different JAXWS specification version. The supported
                  versions are 2.0 and 2.1. Default is 2.1.
..."

This will also require changes in the rg.netbeans.modules.websvc.jaxwsmodel
module because this module uses the internal classes in the jaxws-ri.

Committed the fix to the trunk. Here are the diffs:
http://websvc.netbeans.org/source/browse/websvc/external/jaxws20.zip?rev=1.7&content-type=text/vnd.viewcvs-markup
http://websvc.netbeans.org/source/browse/websvc/jaxws20/nbproject/project.xml?r1=1.4&r2=1.5
http://websvc.netbeans.org/source/browse/websvc/jaxwsmodel/src/org/netbeans/modules/websvc/api/jaxws/wsdlmodel/WsdlPort.java?r1=1.3&r2=1.4
http://websvc.netbeans.org/source/browse/websvc/core/src/org/netbeans/modules/websvc/core/JaxWsUtils.java?r1=1.1&r2=1.2

The jaxws2.1 jars that were used were from the 12/18/2006 build.

More diffs:
http://websvc.netbeans.org/source/browse/websvc/jaxws20/nbproject/project.properties?r1=1.4&r2=1.5
http://websvc.netbeans.org/source/browse/websvc/jaxws20/src/org/netbeans/modules/websvc/jaxws20/jaxws20.xml?r1=1.4&r2=1.5
http://websvc.netbeans.org/source/browse/websvc/jaxwsmodel/src/org/netbeans/modules/websvc/api/jaxws/wsdlmodel/WsdlOperation.java?r1=1.2&r2=1.3
http://websvc.netbeans.org/source/browse/websvc/jaxwsmodel/src/org/netbeans/modules/websvc/api/jaxws/wsdlmodel/WsdlModeler.java?r1=1.2&r2=1.3

The only "API" change that can influence "friend" clients is the following
change in WsdlOperation class:

<    public List<String> getExceptions() {
<        return operation.getJavaMethod().getExceptionsList(); 
<    }

>    public Iterator<String> getExceptions() {
>        return operation.getJavaMethod().getExceptions();
>    }

I would recommend to retain the old method signature to avoid potential problems
 with external clients.

Otherwise, the changes are fine.

I found one another problem

WsdlModeler:setJAXBBindings(URL[] jaxbBindings);

doesn't work.

See the WsdlBindingTest (Unit test)

Need to call WsimportOptions.parseBindings(). However, it is currently not
public in the jaxws-ri. I opened a bug in jaxws-ri 2.1 to make it public.

v.