Posted: Sun Oct 30, 2016 3:41 am Post subject: IIB: Modifying existing webservice operation
Apprentice
Joined: 14 Mar 2011 Posts: 43
I have a webservice with one operation and one input parameter. So i deploy that application and clients start using it. Now I want to add another mandatory input parameter to the same webservice operation. How should i implement this so that my old and new clients continue to use the webservice successfully with old clients need not to change their code. Please let me know how many apps and library versions need to be deployed to achieve this.
You will get different answers to this question depending on who you ask. I tend towards the view that if you add an optional parameter then the new web service can be treated as a new version of the old one. If you add a mandatory parameter then the new web service is effectively a new service - even if its name happens to look similar to the old name.
Quote:
How should i implement this so that my old and new clients continue to use the webservice successfully with old clients need not to change their code. Please let me know how many apps and library versions need to be deployed to achieve this.
Well, clearly your old clients cannot call the new web service because they will not supply the new mandatory parameter. You will need to create a new service, and modify the existing service to become a proxy for the new service. This only works if the new, mandatory parameter can always be given a default value by the proxy. If not, you will be forced to update your clients.
Alternatively, make new clients call the new service, and leave old clients calling the old service. Manage the transition by deprecating the old service and eventually withdrawing it.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum