From: Business Transaction Protocol. Pre-final Draft 0.9 See: http://xml.coverpages.org/OASIS-BTP-Specification-DRAFT090.pdf * XML Schema for SOAP Bindings * Example scenario using SOAP binding -------------------------------------------------------------------------- Example scenario using SOAP binding The example below shows an application request with CONTEXT message sent from client.example.com (which includes the Superior) to services.example.com (Service). soap-http-1 http://client.example.com/soaphandler btpengine 1001 1800 ABC8329045 224352 5 The example below shows CONTEXT_REPLY and a related (and therefore contained) ENROL message sent from services.example.com to client.example.com, in reply to the previous message. There is no application response, so the BTP messages are in the SOAP:Body. soap-http-1 http://client.example.com/soaphandler btpengine 1001 related btpengine 1001 soap-http-1 http://services.example.com/soaphandler AAAB SOAP + Attachments Binding This binding describes how BTP messages will be carried using SOAP as in the SOAP Messages with Attachments specification. It is a superset of the Basic SOAP binding, soap-http-1. The two bindings only differ when application messages are sent Binding name: soap-attachments-http-1 BTP message representation: As for soap-http-1 Mapping for BTP messages (unrelated): As for "soap-http-1" , except the SOAP:Envelope containing the SOAP-Body containing the BTP messages shall be in a MIME body part, as specified in SOAP Messages with Attachments specification. If an application message is being sent at the same time, the mapping for related messages for this binding shall be used, as if the BTP messages were related to the application message(s). Mapping for BTP messages related to application messages: MIME packaging shall be used. One of the MIME multipart/related parts shall contain a SOAP:Envelope, whose SOAP:Headers element shall contain precisely one btp:messages element, containing any BTP messages. Any BTP CONTEXT in the btp:messages is considered to be related to the application message(s) in the SOAP:Body, and to also any of the MIME parts referenced from the SOAP:Body (using the "href" attribute). Implicit messages: As for soap-http-1. Faults: As for soap-http-1. Relationship to other bindings: A BTP address for Superior or Inferior that has the binding string "soap-http-1" is considered to match one that has the binding string "soap-attachements-http-1" if the binding address and additional information fields match. Limitations on BTP use: None Other: As for soap-http-1 Example using SOAP + Attachments binding MIME-Version: 1.0 Content-Type: Multipart/Related; boundary=MIME_boundary; type=text/xml; start="someID" --MIME_boundary Content-Type: text/xml; charset=UTF-8 Content-ID: someID soap-http-1 http://client.example.com/soaphandler 1001 --MIME_boundary Content-Type: text/xml Content-ID: anotherID ABC8329045 224352 5 --MIME_boundary-- XML Schema for SOAP Bindings