Dispatch client works even if port QName is wrong

[socialguy]

Hi,
I noticed that a dispatch client works even if the port QName is wrong. This doesn't make sense. Here's a client that shows the aforementioned behavior:
https://github.com/abhijitsarkar/java-e ... lient.java

[himaiMinh]

Under the jax-ws/jaxws-depoly-desc/src/main/resources/wsdl, there are some wsdl files that specifies the targetnamespace as http://abhijitsarkar.name/webservices/j ... ploy-desc/
I think the author first creates the wsdl and then generates the SEI and SBI for the service.
The client is using the above targetnamespace to create the dispatch client.

[socialguy]

Under the jax-ws/jaxws-depoly-desc/src/main/resources/wsdl, there are some wsdl files that specifies the targetnamespace as http://abhijitsarkar.name/webservices/j ... ploy-desc/
I think the author first creates the wsdl and then generates the SEI and SBI for the service.
The client is using the above targetnamespace to create the dispatch client.

I happen to be the author and no, I didn't start from WSDL, that wasn't the purpose of the project. The purpose was to override some of the annotation values using a webservices.xml.
In any case, a dispatch client shouldn't be able to function with a wrong port QName. When you say "The client is using the above targetnamespace to create the dispatch client", which part of the client code do you refer to? Why do you think how the service was developed (contract first/code first) has any influence on the client?

[fjwalraven]

Answered here.

Regards,
Frits