Closed davidkuehner closed 8 years ago
Thanks for the list. We build our own understanding of backward compatibility into SOA model e.g. adding an optional Schema element often breaks the interface. If a party is receiving the new element that does not understand it, it will raise an error. Unfortunately there only few tools that ignore optional elements. So you have to consider the direction. We build that into our tool. Have a look at:
https://www.wsdl-analyzer.com/diff/show/2023352896?version=1&modifiedVersion=2
to see it in action. You can reverse the direction of the compare and see that you get different results. Much better would be, if you can specify what tools you are using and the lib considers this. But this are Web Services that are made for interoperability. So if there are some tools that break then the interface breaks.
Ok thanks for the info. Is the Difference.breaks() your backward compatibility flag?
yes
Nice. And what means null ? Cannot be defined?
I think so in the meaning of null. You can not tell. But I have not look in the code for a long time.
Feature: Get the list of non-backward compatible Differences between two wsdl files.
Same as WsdlDiffGenerator:compare without the following backward compatible Differences :
Links: