Re: Further along, new problem...

After some further debugging, I'm reaching the conclusion that the 
content type is okay. I set up TcpTunnelGui. This is the SOAP request my 
client is generating:


POST  HTTP/1.0
Host: localhost
Content-Type: text/xml; charset=utf-8
Content-Length: 447
SOAPAction: ""

<?xml version='1.0' encoding='UTF-8'?>
<SOAP-ENV:Envelope xmlns:SOAP-
ENV="http://schemas.xmlsoap.org/soap/envelope/"; 
xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"; 
xmlns:xsd="http://www.w3.org/1999/XMLSchema";>
<SOAP-ENV:Body>
<ns1:getMessage xmlns:ns1="urn:helloworld" SOAP-
ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";>
<caller xsi:type="xsd:string">reader</caller>
</ns1:getMessage>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>


So the content type is set to "text/xml", which looks good to me. 
Anything look wrong with this?

Thanks,
Jason


On Thursday, May 30, 2002, at 01:47  PM, Erich Izdepski wrote:

> In the soap samples directory look at mime/MimeTest.java and the 
> sendFile
> method. Normally a service wouldn't have to set this. By the way, the 
> null
> pointer you are hitting
> should have been thrown as a different exception by the apache code (it 
> is a
> bug).
>
> Erich Izdepski
> Senior Software Engineer
> Cysive, Inc.