• The attachment chosen below is unreferenced by the main message. select None if your endpoint accepts only referenced attachments.
• An attachment is automatically added if a variable in the DIME extended WSDL file is defined as hexBinary or base64Binary. 

We also have an endpoint for server-side SOAP attachment processing, it is at:
                   http://soapclient.com/xml/soapresponder.wsdl
The endpoint supports both SOAP with attachments (SwA) and DIME. Attachments in the request are echoed in the response message using the same attachment method. The server decodes attachments based on the content type in the request message. 

Sample Code (SQLData SOAP Client)

Dim MyAgent As SoapAgent
Set MyAgent = New SoapAgent
'assign parameter values
MyAgent.AddParameter "bstrParam1", "my param 1", ""
MyAgent.AddParameter "bstrParam2", "my param 2", ""
'add an attachment, use DIME encoding
MyAgent.AddAttachment "", "c:\tmp.txt", "", "", "application/dime"
MyAgent.ExecuteMethod "http://soapclient.com/xml/soapresponder.wsdl", "Method1"
'Get the attachment, index is 0 based, 0 is actually the main body.
MyAttachment = MyAgent.GetAttachment(1)

Other Endpoints:

• Bob Cunnings has a RPC style DIME endpoint at http://www.whitemesa.net/wsdl/dime_rpc.wsdl
• Simon Fell offers a DIME endpoint (doc/literal) defined in http://soap.4s4c.com/dime/echo.wsdl .
• Microsoft SOAP TK 3.0 has a DIME endpoint at:
  http://mssoapinterop.org/stkv3/dime/dimeinterop.wsdl