It depends on what the signature tests require. If they restrict what methods can show up in jaxws signatures, we can't have this in a certified release unless a challenge allows the updated api.
The latest spec and API for JAX-WS include significant changes that we need to implement. I realized it when i was looking at the MTOM impl. for JAX-WS.
I.e. there are new Binding URI's that indicate the use of MTOM:
Enable using @BindingType on the endpoint (SEI) implementation class * @BindingType(value=javax.xml.ws.SOAPBinding.SOAP11HTTP_MTOM_BINDING) will enable MTOM on the deployed endpoint for SOAP 1.1 binding
Is there any reason to stick to the current version? I.e. with regard to CTS?
These aren't new, they are part of the 2.0 spec.
Looks like you are right.
At least with regard to the SOAPBinding.
Anyway we do have a stale jaxws source tree in trunk that doesn't reflect the final JAX-WS 2.0 API.
Am i missing something here?