Cast Iron Integration with a SOAP Encoding Endpoint

Cast Iron does not like WSDLs that use SOAP encoding, so this project was a challenge. The input was a comma-separated file, and the output was a SOAP envelope containing the SOAP-encoded array of data required by the service we integrated. Given the nature of the array format, Rapid Integration decided that XSLT was the best option. So, the parsed flat-file becomes multiple parallel arrays in the SOAP envelope, and then we pass the result to the SOAP service. Since the documentation of the target endpoint was not very good, there was some trial and error over a day or so, but we got there in the end.