It seems that the SimpleAxisSever and SimpleAxisWorker in the
org.apache.axis.http are the classes to look into for reading the
SOAP payload I am looking for. And it seems that the former of the
two does in fact open straight server sockets as I originally set forth
to do so that is encouraging.
Dims what do you think ? I still cannot explain the extra characters at
the end of the SOAP message if indeed the ones you were refering to
were only for Axis2. Else they will also explain my issue here in Axis
1.4 as well.
Thanks again
Davanum Srinivas wrote:
Switch off chunking on the client and then read the Content-Length
from the http header. you should read that many bytes from the stream
*AFTER* the end of the http headers (and subsequent blank line).
Actually you are better off using the tcp transport in axis2 client
instead of the http transport. and copy the code inside
org.apache.axis2.transport.tcp.TCPServer to read the payload.
thanks,
dims
On 5/23/07, Demetris G <[EMAIL PROTECTED]> wrote:
Hey Dims,
actually they show up as unprintable characters and they look like
small square boxes ... I am printing the SOAP envelope as text and
it shows up fine but right after the </soapenv:Envelope> I got a bunch
of unprintable characters .. Let me see if indeed they are HTTP
chunking ;)
Thanks
Davanum Srinivas wrote:
> 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]
>>
>>
>
>
---------------------------------------------------------------------
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]
