Excellent! Congrats on working it out. -jeff
-----Original Message----- From: Demetris G [mailto:[EMAIL PROTECTED] Sent: Monday, June 25, 2007 2:20 PM To: [email protected] Subject: Re: SOAP response Hi Jeff, in fact it didn't - for some strange reason the Content-Length comes in as -1 althought the SOAP response is 2000 characters. So I simply re-send it myself after I read the response. And now to the good part - I managed to figure out the issue of the Client stalling - as silly as it sounds, I need to simply close the socket once I am done writing to it and voila the Client accepts the complete message and it is happy. The parsing issue that I had originally is a mystery cause it has not appeared again. So I guess I will need to open the socket to write and then close it once I am done for all the RPC calls to and from the Client. Sounds strange ? Well it works :) Jeff - thanks for all the help and insights so far - I appreciate it and I will continue to keep you and the list updated on these adventures as we are all learning. Walker, Jeff wrote: > Demetris G, > Time for me to ask a stupid question. > Does the value of the "Content-Length: " http header of your response > match the length of all of the actual sent characters? > -jeff > > > -----Original Message----- > From: Demetris G [mailto:[EMAIL PROTECTED] > Sent: Saturday, June 23, 2007 10:33 PM > To: [email protected] > Subject: Re: SOAP response > > > Hi all, > > is it possible that no one working with Axis for a while now knows > what terminates > the SOAP message coming from the server engine ?? Anyone ? I will > appreciate it. > Nothing shows up in the tcpmon or any other tool I used however the SAX > parser > see the complete SOAP envelope as shown below but yet it block waiting > for something > else. What is this extra data that it is expecting ? I am sifting > through the Axis/SAX > classes but it takes a long time to chase this. > > Thanks much > > Demetris G wrote: > >> Jeff -- I traced the SAX and Xerces routines to find out what they are >> > > >> doing but it >> gets a bit hectic to figure them out. I know the client reads back the >> > > >> headers I send >> it and all of the SOAP message below (if for example I mispell the >> last tag of the SOAP >> message then SAX is complaining which means it does parse it till >> them). But the parser >> is stuck on SocketInputStream.read() as if it is expecting more after >> the last tag of the >> SOAP message - I tried CR / LF but that does not do it. >> >> Any suggestions ?? >> >> "<?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:Body>" >> "<ns1:getBundlesResponse >> soapenv:encodingStyle=\"" >> >> "http://schemas.xmlsoap.org/soap/encoding/\"; " >> >> "xmlns:ns1=\"http://soapobject.bundle.org\";>" >> "<getBundlesReturn >> soapenc:arrayType=\"xsd:long[24]\" xsi:type=\"soapenc:Array\" " >> >> "xmlns:soapenc=\"http://schemas.xmlsoap.org/soap/encoding/\";>" >> "<getBundlesReturn >> href=\"#id23\"/>" >> "</getBundlesReturn>" >> "</ns1:getBundlesResponse>" >> "<multiRef id=\"id23\" >> soapenc:root=\"0\" " >> >> "soapenv:encodingStyle=\"http://schemas.xmlsoap.org/soap/encoding/\"; " >> "xsi:type=\"xsd:long\" >> xmlns:soapenc=\"http://schemas.xmlsoap.org/soap/encoding/\";>" >> "3" >> "</multiRef>" >> "</soapenv:Body>" >> "</soapenv:Envelope>"; >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
