Handling of "loosely typed" 3rd party WSDL files
As part of a development project, we were required to consume an existing 3rd party web service, but were unable to import their published WSDL in JADE due to the fact that their generic response definitions were not strongly typed. The definition just included
xmlns:soap-enc="http://schemas.xmlsoap.org/soap/encoding/" in definitions, and
inside the response definitions.
Effectively this is defining the response as "an array of XML fields" which JADE would not know how to deal with during the parsing of the response. Since this is technically a valid way to specify a response (although not advisable IMO), it would be good if JADE could deal with this type of definition. Perhaps the generated response class could just have a JadeXMLElementArray property created, which was populated with the contents of the named Array element at parse time. It would obviously then be up to the developer to manually process the resulting JadeXMLElement items in the array, but at least the web service would be usable.