Win a copy of Rust Web Development this week in the Other Languages forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Tim Cooke
  • Campbell Ritchie
  • Ron McLeod
  • Liutauras Vilda
  • Jeanne Boyarsky
Sheriffs:
  • Junilu Lacar
  • Rob Spoor
  • Paul Clapham
Saloon Keepers:
  • Tim Holloway
  • Tim Moores
  • Jesse Silverman
  • Stephan van Hulst
  • Carey Brown
Bartenders:
  • Al Hobbs
  • Piet Souris
  • Frits Walraven

Support multiple web services WSDL @ one client location.

 
Ranch Hand
Posts: 1249
Spring Java Ubuntu
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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?
 
Ranch Hand
Posts: 1376
Eclipse IDE Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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.
 
Rancher
Posts: 43027
76
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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
Ranch Hand
Posts: 1249
Spring Java Ubuntu
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

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
Rancher
Posts: 43027
76
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
The idea would be that the client migrates to the newer version - thus obviating the need to keep different code bases.
 
You showed up just in time for the waffles! And this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
https://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton
reply
    Bookmark Topic Watch Topic
  • New Topic