Regarding SOAP clients backward compatibility for service name change

One of a internal web service provider provides the SOAP RPC API to connect to their system. Recently they changed their service name that gets reflected from their wsdl.

For e.g if the service was previously "MyService", it has been changed to "MyService1" but the address location remains the same.

<wsdl:service name="MyService">
<wsdl:port binding="tns:MyServiceSoapBinding" name="APIImplPort">
<soap:address location="http://ift.tt/1LadspH"/>
</wsdl:port>
</wsdl:service>


<wsdl:service name="MyService1">
<wsdl:port binding="tns:MyService1SoapBinding" name="APIImplPort">
<soap:address location="http://ift.tt/1LadspH"/>
</wsdl:port>
</wsdl:service>

Will it require to change the existing clients or will they work without any change?

Specifically, I am using java along with spring JaxWsPortProxyFactoryBean to connect to the above web service. I can see that I have to change the service name to make it work but I am not sure whether this is due to the underlying mechanism(spring JaxWsPortProxyFactoryBean) that I have to change the service name to make it work or otherwise that can work with any other technology without any change(for e.g .NET).