How many use cases are there? Your example is equivalent to adding a not null field.
Shouldn't your regression test suite catch that? I mean say you drop a optional field. Now that may or may not be backward compatible depending upon whether that field was used in the context of your specific project. I don't deny the usefulness of a generic tool. Mahesh On Tue, Aug 23, 2011 at 3:34 PM, Daniel Kulp <[email protected]> wrote: > On Tuesday, August 23, 2011 9:23:36 AM dstainer wrote: > > I'm curious if there are any tools available that test backwards > > compatibility between two versions of the same WSDL's i.e. > > somefile-v1_0.wsdl and somefile-v1.1.wsdl? > > > > For example, I'm looking for a tool that would recognize that if I added > a > > parameter to a request type with a minOccurs="0" that is a backwards > > compatible change. However, if that same parameter is added but marked as > > minOccurs="1" then you've broken compatibility. That is one of a number > of > > use cases for backwards and non-backwards compatibility that I'd like to > > test for. > > > > Is there anything like that? > > I've never seen anything like that. Definitely and interesting idea. If > you find anything, please let us know. :-) > > Dan > > > > > > Thanks > > Derek > > > > -- > > View this message in context: > > > http://cxf.547215.n5.nabble.com/Are-tools-available-to-test-backwards-compa > > tibility-of-WSDL-s-tp4727313p4727313.html Sent from the cxf-user mailing > > list archive at Nabble.com. > -- > Daniel Kulp > [email protected] > http://dankulp.com/blog > Talend - http://www.talend.com >
