The following (portions of) WSDL files are valid and equivalent, however assertXMLEqual does not seem to allow for unordered lists of elements.
(i.e. assertXMLEqual on "<test><foo>abc</foo><foo>123</foo></test>" and "<test><foo>123</foo><foo>abc</foo></test>" would result in an AssetionFailedError.) WSDL File 1: <wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; xmlns:ns0="http://tempuri.org"; targetNamespace="http://tempuri.org";> <wsdl:message name="retUIntRequest"> <wsdl:part name="parameters" element="ns0:retUInt"/> </wsdl:message> <wsdl:message name="retByteArrayRequest"> <wsdl:part name="parameters" element="ns0:retByteArray"/> </wsdl:message> </wsdl:definitions> WSDL File 2: <wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; xmlns:ns0="http://tempuri.org"; targetNamespace="http://tempuri.org";> <wsdl:message name="retByteArrayRequest"> <wsdl:part name="parameters" element="ns0:retByteArray"/> </wsdl:message> <wsdl:message name="retUIntRequest"> <wsdl:part name="parameters" element="ns0:retUInt"/> </wsdl:message> </wsdl:definitions> Would it be acceptable to patch XMLUnit to allow these two comparisons (the strings and WSDL files) to pass? Is that work already underway? If I create the patch, how can I submit it?? Thank you, Brian Murray Software Engineer, WebSphere Application Server Development IBM Corporation, 4205 S Miami Blvd, Durham NC 27709 (919) 486-2087 ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Xmlunit-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xmlunit-general
