Reputation: 262684
Are there any guidelines/tutorials as to how to handle the evolution of a SOAP web service?
I can see that changing existing methods or types would probably not work, but can I just add new methods, complex types, enumeration values without breaking existing clients?
Upvotes: 5
Views: 401
Reputation: 2736
Basically you shouldn't modify existing WebService but you can safely extend it by:
In our team we handle WebService evolution by putting version number in namespace, so every time we do non backward compatible changes we release new WebService with separate namespace. As a side effect way we have to maintain 2-3 versions/instances of WebServices until our customers migrate themselves (we give them some time until we stop supporting older versions).
Upvotes: 4