« Web service versioning | Main | Web service versioning and the consumer does not need to know about... »
June 19, 2006
Convertible and unconvertible Web service changes
I'm thinking about the possibility to convert incoming SOAP messages so that they conform to the current WSDL. Therefore I'd like to list up all possible changes to a message and if these are convertible or not.
My list so far:
- Changing Operation Name: convertible
- Adding an operation: no influence on existing service
- Deleting an operation: not convertible
- Changing parameter name: convertible
- Adding a parameter: convertible (use default value)
- Deleting a parameter: not convertible
- Combining parameters to a complex object (or other way round): convertible
- Changing parameter order: convertible (or no influence?)
- Changing data types of parameters (simple data types, complex objects, hierarchy or not?): may be possible to convert for simple data types and objects in a hierarchy
- Changing return data type: same as above
You can think of the XML elements on their own, too:
- Renaming an element: convertible
- Adding an element: convertible (default value)
- Deleting an element: not convertible
- Changing from element to attribute (and other way round): convertible
- Moving a node up or down in the XML tree: convertible
Can you think of other changes? I have to think of how convertible parts can be converted (something like mapping functions).
Posted by Dominik Marks at June 19, 2006 11:59 AM