The task is to create a SOAP message that will be transported over several integration-platforms(IP).
The message is not a true SOAP message. It has only the structure of a SOAP message with routing information and XML DSIG in the header.
The SOAP-body/payload is treated as a "byte-array/blob" in the "IP world" and the sender is responsible to give the SOAP body the correct data for the Receiver . The XML DSig is used to give the SOAP-message a verifiable signatur placed in the SOAP header. The XML DSig signature includes the SOAP body and som of the SOAP header tags.
Creation of a GUI testprogram in C# VS 2005 that takes a "payload" as a file, fields for all the routing info as GUI fields and creates a SOAP message with the "payload-file" in the SOAP-body and the routing GUI filelds as SOAP header and add a XML DSig signature to the SOAP header.
The payload file could be "whatever". Importent is to isolate the SOAP body content so it NOT disturb the SOAP structure itself. (= XML within a SOAP, text containing data that can be interpeeted as <tag>, totaly unknown data structure= binary=images ). The SOAP body could also contains a true SOAP body for a Web Service.
Why this approach with SOAP and not using Web Services and WSDL??
* Because we want to use the SOAP structure to route the message thru several Integration Platforms using a standard parser for SOAP.
* The Sender creates a SOAP body for the receiver. This Testprogram "dress" the body with all the other SOAP properties including the SOAP header.
* The Sender do not need to know how to create routing information for the message. (The routing informatuion is rapidly changed)
* The Sender do not need to know how make a Signature on th SOAP message
* The Receiver can rely that the message is unchanged thru the mechanism of XML DSign