Dims,

Thanks for the timely response!  I am pleasantly surprised you are reading mail from 
this list :-).

Srilekha,

This list is for Apache SOAP, an older generation implementation compared to Axis, 
which supports JAX-RPC, SOAP 1.2, WSDL, DIME, etc., that Apache SOAP does not.  I 
suggest you direct future questions to an Axis list (e.g. [EMAIL PROTECTED]) for the 
best answers.

Thanks.

Scott Nichol

Do not send e-mail directly to this e-mail address,
because it is filtered to accept only mail from
specific mail lists.
----- Original Message ----- 
From: "Davanum Srinivas" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, December 01, 2003 10:25 AM
Subject: Re: soap over tcp


> try stream.flush() after calling soapmessage.writeTo(stream);
> 
> --- Srilekha Mudumbai <[EMAIL PROTECTED]> wrote:
> > Group,
> > 
> > I have a question on soapmessage.writeTo(stream);
> > 
> > When I send it over a TCP socket, it does not send the last line of the soap
> > message, esp. </soap:Envelope>
> > 
> > The server side keeps on waiting for this piece to arrive. Why is it 
> > happening
> > if it is a socket connection? It can wait for the response after sending the
> > whole message to the server. Why should it hold a piece of the request to
> > itself.
> > 
> > If the stream is System.out or a ByteArrayOutputStream or anything local,
> > everything works fine.
> > 
> > I would like some suggestions from the users to troubleshoot this issue.
> > 
> > Regards
> > Srilekha
> > 
> > 
> > 
> > 
> 
> 
> =====
> Davanum Srinivas - http://webservices.apache.org/~dims/
>

Reply via email to