Hi All,
I have created a SOAP Message with attachment and it
doesn't contain a MIME Header. I meansit doesnt follow the format
of SOAP Message given below. My request message also differ from the
one which Scott send to this group a few days before.
My problem is the first header(MIMe-Version 1.0
Content-Type:Multipart/related.. etc etc ) is not coming in my request message.
Also there is no reference of the attachment in SOAP Envelope as Dheeraj
said in January end mail :)
But it do have separate headers for the SOAPBody and
attachment parts.
So does that mean my SOAPMEssage is not MIME encoded?
Please help.. I am attaching my request message
<<soapInMsgMail.txt>>
Scott, Dheeraj and all .. Any inputs will help me
..
Thanks & Regards
Dhanush
MIME-Version: 1.0 Content-Type: Multipart/Related; boundary=MIME_boundary; type=text/xml; start="<http://claiming-it.com/claim061400a.xml>" Content-Description: This is the optional message description. --MIME_boundary Content-Type: text/xml; charset=UTF-8 Content-Transfer-Encoding: 8bit Content-ID: <http://claiming-it.com/claim061400a.xml> Content-Location: http://claiming-it.com/claim061400a.xml <?xml version='1.0' ?> <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"> <SOAP-ENV:Body> .. <theSignedForm href=""/> .. </SOAP-ENV:Body> </SOAP-ENV:Envelope> --MIME_boundary Content-Type: image/tiff Content-Transfer-Encoding: binary Content-ID: <http://claiming-it.com/claim061400a.tiff> Content-Location: http://claiming-it.com/claim061400a.tiff ...binary TIFF image... --MIME_boundary--
|
------=_Part_0_12893236.1085474330169 Content-Type: text/xml; charset=UTF-8 Content-Transfer-Encoding: binary Content-Id: <4E68062CC1BCDFE77423618AE3645694> <?xml version="1.0" encoding="UTF-8"?> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <soapenv:Header> <ns1:fileName1 soapenv:mustUnderstand="0" xsi:type="xsd:string" xmlns:ns1="Header">WLan-IBm.pdf</ns1:fileName1> <ns2:fileName2 soapenv:mustUnderstand="0" xsi:type="xsd:string" xmlns:ns2="Header">sil.bmp</ns2:fileName2> <ns3:fileName3 soapenv:mustUnderstand="0" xsi:type="xsd:string" xmlns:ns3="Header">dhanush.txt</ns3:fileName3> </soapenv:Header> <soapenv:Body> <ns4:putMessage soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns4="urn:webservices.oexgateway.bt.com"> <in0 href="#id0"/> </ns4:putMessage> <multiRef id="id0" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns5:OAGMessage" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns5="urn:webservices.oexgateway.bt.com"> <aqMessageID xsi:type="xsd:string" xsi:nil="true"/> <docRefNum xsi:type="xsd:string" xsi:nil="true"/> <documentID xsi:type="xsd:string" xsi:nil="true"/> <messagePayload xsi:type="xsd:string" xsi:nil="true"/> <messageStatus xsi:type="xsd:int">0</messageStatus> <oagDocType xsi:type="ns5:OAGDocType" xsi:nil="true"/> <partySiteID xsi:type="xsd:string" xsi:nil="true"/> <recipientID xsi:type="xsd:string" xsi:nil="true"/> <senderID xsi:type="xsd:string" xsi:nil="true"/> </multiRef> </soapenv:Body> </soapenv:Envelope> ------=_Part_0_12893236.1085474330169 Content-Type: application/octet-stream Content-Transfer-Encoding: binary Content-Id: <5AEE80B689A34337F1B38E8B03011551> %PDF-1.2 %âãÏÓ 799 0 obj << /Linearized 1 /O 802 /H [ 935....