Support multiple web services WSDL @ one client location.

[Shaan Shar]

So imagine if we are acting as a Web service client and our Web Service provider is making changes very frequently and somehow because of the complexity and size, not all the time, we can match with our server. There could be number of reasons because of which we may need to support multiple WSDL support at client side so that we can react accordingly.

Would like to seek advise from various people, how did they resolve this issue while Web services were picked up by Industry?

[Abhay Agarwal]

it depends upon your client configuration. we can use wsdl binding customization to maintain wsdl changes. For each wsdl, you have to define new client code.

[Ulf Dittmer]

The WS provider should not turn off the previous version of a WS rigth when a new one is released. They should either use some kind of API versioning, or different URLs to separate the WS. And then they should give the client a certain amount of time (3, 6, 12, ... month) to upgrade the client before an older version of the service is turned off.

[Shaan Shar]

Ulf Dittmer wrote:The WS provider should not turn off the previous version of a WS rigth when a new one is released. They should either use some kind of API versioning, or different URLs to separate the WS. And then they should give the client a certain amount of time (3, 6, 12, ... month) to upgrade the client before an older version of the service is turned off.

I think even if Service provider gives us that amount of time and provide different versioning for API's, Client needs to maintain different code for different version of Services.. and I guess that's what the major problem, to keep different code base for different versions...

[Ulf Dittmer]

The idea would be that the client migrates to the newer version - thus obviating the need to keep different code bases.