Thanks Demis, one again I agree with you 100% about the soap/wsdl point of view and if I have to choose, I go for “Add ServiceStack Reference”
But the point here is that a built-in SS feature (support for wsdl with custom ns → “Config.WsdlServiceNamespace”) is not fully working: are you considering to review the wsdl generation?
that workaround may resolve the wsdl itself, but it compromised its purpose: create a client proxy able to send a valid request and handle/deserialize a response.
Said so. since we are not using via soap non of the SS operations, we actually totally removed from the WSDL, but maybe only one SS type (ResponseStatus), we go for the wsdl customization you propsed or we try to avoid to use also that type as well as per my other current open post.