That's not garbled data you are getting. that's called HTTP chunking :) you are getting numbers right?
you can switch 'em off on the client. See http://wso2.org/library/952 -- dims On 5/23/07, Demetris G <[EMAIL PROTECTED]> wrote:
I have been sending emails to the list asking about this for a bit now and a few good people certainly jumped in to help and I more than appreciate that. With some searches also on the web I am finding the Fiddlers and the Soap Extensions and all the good stuff out there including the tcpMon and the sniffers to record SOAP exchanges. However, I am still to find the simple good old way for one to open a server socket, have the client stubs write to it and read and good old SOAP message. What am I missing guys ? Has this simplest of simple things never been done before? It is hard to believe that no one ever attempted to write a small routine inside an application to read a complete SOAP message as an XML doc and parse it. Am I just barking at wrong tree looking for the wrong things or am I missing something obvious? Any pointers as to why when I try to do this I am getting garbled data at the end of the SOAP messages. These are simple remote calls - what are they carrying at their tail end and why? Where would one find the high-level protocol description with which the stubs are employing to communicate with a remote web service? Thanks once again - and by the way ; Axis rocks .. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Davanum Srinivas :: http://davanum.wordpress.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
