Why does JAX-WS clients need WSDL access?
The requirement that a JAX-WS based client needs access to the WSDL even if generated from a WSDL in the first place is a real pain. If wsimport can compile the WSDL into artifacts why does JAX-WS at runtime need to do it again?
In the cases I have to deal with the WSDL is not readily available, i.e. it is provided off-line, and I need to modify it any way because wsimport doesn't like it in its original form in the first place.
Now I somehow have to bundle it with my client apps, may be use catalogs to access it, etc.. If JAX-WS was suppose to make things easier it seems to fail badly here.
I am not aware that other toolchains require the WSDL to be available to the client at run-time if the client is based on generated artifcats.