<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">On 28 Apr 2020, at 11:03, James Darling <<a href="mailto:james@abscond.org" class="">james@abscond.org</a>> wrote:<br class=""><div><blockquote type="cite" class=""><br class="Apple-interchange-newline"><div class=""><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">This taught me that not all SOAP APIs are particularly strict at following standards</span></div></blockquote></div><br class=""><div class="">This reminds me of a commercial SOAP API I came across once, which was a wrapper round an older CLI. The XML was horrendously complicated, but specified to the nth degree in schemas. After a particularly head-scratchy debugging session, I eventually realised that the names and types of the child elements you passed in were completely ignored, and it just passed them straight through as arguments to the CLI, in whichever order you included them in your request.</div><div class=""><br class=""></div><div class="">Kerry</div></body></html>