The comparison does not seem to take extensions into account

[frabac72]

In the code that my WSDL and XSD file are generated from I have a few classes extending other classes. That results in some of the complex types in my XSD being the extension of other complex types. For instance: <xs:complexType name="changePaymentDayChanges"> xs:complexContent <xs:extension base="tns:scheduleChanges"> xs:sequence <xs:element name="billingDayDelta" type="xs:int"/> <xs:element minOccurs="0" name="changePaymentDayParameters" type="tns:changePaymentDay"/> <xs:element name="previousBillingDay" type="xs:int"/> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> In the two versions I am comparing, scheduleChanges changed. For the operations in the WSDL that use scheduleChanges directly, the change is reported, for instance: Definitions: PortType ExtendedRescheduleEnquiryService: Operation loadRescheduleInformation: Output: Message loadRescheduleInformationResponse: Part result: Element loadRescheduleInformationResponse: ComplexType http://ws.chpconsulting.com/alfa/reschedule/v1/enquiry/loadRescheduleInformationResponse: Sequence: Element return: ComplexType http://ws.chpconsulting.com/alfa/reschedule/v1/scheduleChanges: ... On the contrary, no mention is made that changePaymentDayChanges has changed (and that the operations using it are affected).

Any idea what I can do to bridge this apparent gap with extensions?

Thanks!

[predic8]

Thanks for reporting.

[frabac72]

I would be happy to discuss the workaround I adopted, maybe not here though?

[predic8]

Hi @frabac72, thanks for thoughts. SOA Model has not a high priority on our list anymore since Web Services and XML Schema are outdated. He make updates from time to time when we ourself need something. Feel free to fix the code and send a pull request if you want to.