Setting mime headers for MessageFactory.createMessage(...)

Question

Hi-,
I am trying to read the attached SOAP1.1 w/ attc. message from a plain file with a piece of simple Java code. The 'MessageFactory.createMessage(MimeHeaders headers, java.io.InputStream in)' is not very informative as to what goes in for headers, so I tried all of the below commented headers - no luck, only exceptions. Any explanation as to what I am doing wrong? I am using JWSDP1.5 with J2SE5.0.
=============JAVA CODE=================
public class SOAPTest {
static public void main(String[] args) throws SOAPException, IOException
MimeHeaders headers = new MimeHeaders();
//headers.addHeader("Content-Type","multipart/related");
//headers.addHeader("Content-Location","");
//headers.addHeader("Content-Type","text/xml; charset=UTF-8");
//headers.addHeader("Content-Type","text/xml");
//headers.addHeader("Content-Transfer-Encoding","8Bit");
//headers.addHeader("Content-Transfer-Encoding","Binary");
//headers.addHeader("Content-Type","application/pdf");
MessageFactory factory = MessageFactory.newInstance();
InputStream sample = new FileInputStream(args[0]);
SOAPMessage message = factory.createMessage(headers,sample);
System.out.println("Soap Header\n:"+message.getSOAPHeader());
sample.close();
=============SOAP message w/ ATTC.=================
MIME-Version: 1.0
Content-Type: multipart/related; boundary=4444741.1049296259836.MIMEBoundary; type="text/xml"
Content-Description: Acknowledgement - P20030811030857.0504
--4444741.1049296259836.MIMEBoundary
Content-Type: text/xml; charset=UTF-8
Content-Transfer-Encoding: 8bit
Content-Location: Envelope1120
<?xml version="1.0" encoding="UTF-8"?>
<SOAP:Envelope xmlns="http://www.irs.gov/efile" xsi:schemaLocation="http://schemas.xmlsoap.org/soap/envelope/ 2004v1.0/Common/SOAP.xsd http://www.irs.gov/efile 2004v1.0/Common/efileMessage.xsd" 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" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:efile="http://www.irs.gov/efile">
<SOAP:Header>
<efile:AcknowledgementHeader transmissionVersion="1.0">
<AcknowledgementTimestamp>2003-10-20T16:15:33+05:00</AcknowledgementTimestamp>
</efile:AcknowledgementHeader>
</SOAP:Header>
<SOAP:Body>
<efile:AcknowledgementManifest count="2">
<Reference contentLocation="TID01"/>
<Reference contentLocation="Return0001"/>
</efile:AcknowledgementManifest>
</SOAP:Body>
</SOAP:Envelope>
--4444741.1049296259836.MIMEBoundary
Content-Type: text/xml; charset=UTF-8
Content-Transfer-Encoding: 8bit
Content-Location: TID01
<?xml version="1.0" encoding="UTF-8"?>
<TransmissionAcknowledgement xmlns="http://www.irs.gov/efile" xmlns:efile="http://www.irs.gov/efile" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.irs.gov/efile 2004v1.0/Common/efileMessage.xsd" transmissionVersion="1.0"><TransmissionId>TID01</TransmissionId><TransmissionTimestamp>2003-10-20T15:25:36+05:00</TransmissionTimestamp><TransmissionStatus>A</TransmissionStatus><GTXKey>P20030811030857.0504</GTXKey></TransmissionAcknowledgement>
--4444741.1049296259836.MIMEBoundary
Content-Type: text/xml; charset=UTF-8
Content-Transfer-Encoding: 8bit
Content-Location: Return0001
<?xml version="1.0" encoding="UTF-8"?>
<ReturnAcknowledgement xmlns="http://www.irs.gov/efile" xmlns:efile="http://www.irs.gov/efile" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.irs.gov/efile 2004v1.0/Common/efileMessage.xsd" returnVersion="2004v1.0" validatingSchemaVersion="2004v1.0"><ReturnId>01000020032881234567</ReturnId><FilerEIN>010000000</FilerEIN><ReturnType>1120</ReturnType><TaxYear>2004</TaxYear><ReturnStatus>A</ReturnStatus><CompletedValidation>yes</CompletedValidation><PaymentIndicator>Payment Request Received</PaymentIndicator></ReturnAcknowledgement>
--4444741.1049296259836.MIMEBoundary--

Answer 1

Never mind. I fixed it - it turned out that the first MIME headers are the "protocol specific" stuff. Once I transfered them to the MessageFactory, all worked out well.