You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Rich Adili <Ri...@xata.com> on 2007/05/23 21:49:57 UTC

Logging SOAP requests?

Hi,

How does one go about logging the outgoing SOAP requests?

Rich Adili

RE: Logging SOAP requests?

Posted by Rich Adili <Ri...@xata.com>.
Hi dims,

Thanks! That's just what I need for my product design. However, I'm also
babysitting a legacy application written around an Axis1.4 beta, I
forget exactly which beta. Do you know if this technique also applies to
the older code?

Rich

-----Original Message-----
From: Davanum Srinivas [mailto:davanum@gmail.com] 
Sent: Wednesday, May 23, 2007 3:06 PM
To: axis-user@ws.apache.org
Subject: Re: Logging SOAP requests?

Rich,

See http://blogs.cocoondev.org/dims/archives/004668.html

thanks,
dims

On 5/23/07, Rich Adili <Ri...@xata.com> wrote:
>
>
>
>
> Was thinking in terms of an option that field personnel could flip on
and
> off. Debugging proxies are a bit arduous for such folks. I'm surprised
a
> simple logging mechanism isn't built in.
>
>
>
>  ________________________________
>
>
> From: robert lazarski [mailto:robertlazarski@gmail.com]
>  Sent: Wednesday, May 23, 2007 3:01 PM
>  To: axis-user@ws.apache.org
>  Subject: Re: Logging SOAP requests?
>
>
>
>
> If you are talking about writing them to a file / db via log4j , look
at the
> modules guide and their howto on writing a logging module:
>
>  http://ws.apache.org/axis2/1_2/modules.html
>
>  If you just want to look at it, try tcpmon or the soapmonitor.
>
>  HTH,
>  Robert
>
>
> On 5/23/07, Rich Adili < Rich.Adili@xata.com> wrote:
>
>
> Hi,
>
> How does one go about logging the outgoing SOAP requests?
>
> Rich Adili
>
>


-- 
Davanum Srinivas :: http://davanum.wordpress.com

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org

Re: Logging SOAP requests?

Posted by Davanum Srinivas <da...@gmail.com>.
If you used Axis1's commons http sender..yes.

-- dims

On 5/29/07, Doug Schaible <do...@gmail.com> wrote:
> Dims,
>
> Would this also work for Axis 1?
>
> Thanks,
> Doug
>
>
> On 5/23/07, Davanum Srinivas <da...@gmail.com> wrote:
> >
> > Rich,
> >
> > See http://blogs.cocoondev.org/dims/archives/004668.html
> >
> > thanks,
> > dims
> >
> > On 5/23/07, Rich Adili <Ri...@xata.com> wrote:
> > >
> > >
> > >
> > >
> > > Was thinking in terms of an option that field personnel could flip on
> and
> > > off. Debugging proxies are a bit arduous for such folks. I'm surprised a
> > > simple logging mechanism isn't built in.
> > >
> > >
> > >
> > >  ________________________________
> > >
> > >
> > > From: robert lazarski [mailto:robertlazarski@gmail.com]
> > >  Sent: Wednesday, May 23, 2007 3:01 PM
> > >  To: axis-user@ws.apache.org
> > >  Subject: Re: Logging SOAP requests?
> > >
> > >
> > >
> > >
> > > If you are talking about writing them to a file / db via log4j , look at
> the
> > > modules guide and their howto on writing a logging module:
> > >
> > >  http://ws.apache.org/axis2/1_2/modules.html
> > >
> > >  If you just want to look at it, try tcpmon or the soapmonitor.
> > >
> > >  HTH,
> > >  Robert
> > >
> > >
> > > On 5/23/07, Rich Adili < Rich.Adili@xata.com> wrote:
> > >
> > >
> > > Hi,
> > >
> > > How does one go about logging the outgoing SOAP requests?
> > >
> > > Rich Adili
> > >
> > >
> >
> >
> > --
> > Davanum Srinivas :: http://davanum.wordpress.com
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> axis-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-user-help@ws.apache.org
> >
> >
>
>


-- 
Davanum Srinivas :: http://davanum.wordpress.com

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org

Re: Logging SOAP requests?

Posted by Doug Schaible <do...@gmail.com>.
Dims,

Would this also work for Axis 1?

Thanks,
Doug


On 5/23/07, Davanum Srinivas <da...@gmail.com> wrote:
>
> Rich,
>
> See http://blogs.cocoondev.org/dims/archives/004668.html
>
> thanks,
> dims
>
> On 5/23/07, Rich Adili <Ri...@xata.com> wrote:
> >
> >
> >
> >
> > Was thinking in terms of an option that field personnel could flip on
> and
> > off. Debugging proxies are a bit arduous for such folks. I'm surprised a
> > simple logging mechanism isn't built in.
> >
> >
> >
> >  ________________________________
> >
> >
> > From: robert lazarski [mailto:robertlazarski@gmail.com]
> >  Sent: Wednesday, May 23, 2007 3:01 PM
> >  To: axis-user@ws.apache.org
> >  Subject: Re: Logging SOAP requests?
> >
> >
> >
> >
> > If you are talking about writing them to a file / db via log4j , look at
> the
> > modules guide and their howto on writing a logging module:
> >
> >  http://ws.apache.org/axis2/1_2/modules.html
> >
> >  If you just want to look at it, try tcpmon or the soapmonitor.
> >
> >  HTH,
> >  Robert
> >
> >
> > On 5/23/07, Rich Adili < Rich.Adili@xata.com> wrote:
> >
> >
> > Hi,
> >
> > How does one go about logging the outgoing SOAP requests?
> >
> > Rich Adili
> >
> >
>
>
> --
> Davanum Srinivas :: http://davanum.wordpress.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>

SOAP Messages

Posted by Demetris G <de...@ece.neu.edu>.
The Client proxy class serialize the SOAP message before it sends it 
out. Is that
a true statement? If yes, does anyone know which classes in the baseline 
perform that?

Thanks


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org

Re: Logging SOAP requests?

Posted by Davanum Srinivas <da...@gmail.com>.
Rich,

See http://blogs.cocoondev.org/dims/archives/004668.html

thanks,
dims

On 5/23/07, Rich Adili <Ri...@xata.com> wrote:
>
>
>
>
> Was thinking in terms of an option that field personnel could flip on and
> off. Debugging proxies are a bit arduous for such folks. I'm surprised a
> simple logging mechanism isn't built in.
>
>
>
>  ________________________________
>
>
> From: robert lazarski [mailto:robertlazarski@gmail.com]
>  Sent: Wednesday, May 23, 2007 3:01 PM
>  To: axis-user@ws.apache.org
>  Subject: Re: Logging SOAP requests?
>
>
>
>
> If you are talking about writing them to a file / db via log4j , look at the
> modules guide and their howto on writing a logging module:
>
>  http://ws.apache.org/axis2/1_2/modules.html
>
>  If you just want to look at it, try tcpmon or the soapmonitor.
>
>  HTH,
>  Robert
>
>
> On 5/23/07, Rich Adili < Rich.Adili@xata.com> wrote:
>
>
> Hi,
>
> How does one go about logging the outgoing SOAP requests?
>
> Rich Adili
>
>


-- 
Davanum Srinivas :: http://davanum.wordpress.com

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org

Re: Capturing SOAP messages

Posted by Demetris G <de...@ece.neu.edu>.
I think switching off the chunking is certainly something I can use.
By the way I am working with Axis 1.4 on this one so I guess I will
stick with http.I guess to read the payload I can find the
corresponding class??

Thanks Dims

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 <de...@ece.neu.edu> 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 <de...@ece.neu.edu> 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: axis-user-unsubscribe@ws.apache.org
>> >> For additional commands, e-mail: axis-user-help@ws.apache.org
>> >>
>> >>
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>
>>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org

Re: Capturing SOAP messages

Posted by Demetris G <de...@ece.neu.edu>.
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 <de...@ece.neu.edu> 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 <de...@ece.neu.edu> 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: axis-user-unsubscribe@ws.apache.org
>> >> For additional commands, e-mail: axis-user-help@ws.apache.org
>> >>
>> >>
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>
>>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org

Re: Capturing SOAP messages

Posted by Davanum Srinivas <da...@gmail.com>.
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 <de...@ece.neu.edu> 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 <de...@ece.neu.edu> 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: axis-user-unsubscribe@ws.apache.org
> >> For additional commands, e-mail: axis-user-help@ws.apache.org
> >>
> >>
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>


-- 
Davanum Srinivas :: http://davanum.wordpress.com

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org

Re: Capturing SOAP messages

Posted by Demetris G <de...@ece.neu.edu>.
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 <de...@ece.neu.edu> 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: axis-user-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>
>>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org

Re: Capturing SOAP messages

Posted by Davanum Srinivas <da...@gmail.com>.
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 <de...@ece.neu.edu> 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: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>


-- 
Davanum Srinivas :: http://davanum.wordpress.com

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org

Capturing SOAP messages

Posted by Demetris G <de...@ece.neu.edu>.
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: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org

RE: Logging SOAP requests?

Posted by Rich Adili <Ri...@xata.com>.
Was thinking in terms of an option that field personnel could flip on
and off. Debugging proxies are a bit arduous for such folks. I'm
surprised a simple logging mechanism isn't built in.

 

________________________________

From: robert lazarski [mailto:robertlazarski@gmail.com] 
Sent: Wednesday, May 23, 2007 3:01 PM
To: axis-user@ws.apache.org
Subject: Re: Logging SOAP requests?

 

If you are talking about writing them to a file / db via log4j , look at
the modules guide and their howto on writing a logging module: 

http://ws.apache.org/axis2/1_2/modules.html 

If you just want to look at it, try tcpmon or the soapmonitor. 

HTH,
Robert 

On 5/23/07, Rich Adili < Rich.Adili@xata.com
<ma...@xata.com> > wrote:

Hi,

How does one go about logging the outgoing SOAP requests?

Rich Adili

Re: Logging SOAP requests?

Posted by robert lazarski <ro...@gmail.com>.
If you are talking about writing them to a file / db via log4j , look at the
modules guide and their howto on writing a logging module:

http://ws.apache.org/axis2/1_2/modules.html

If you just want to look at it, try tcpmon or the soapmonitor.

HTH,
Robert

On 5/23/07, Rich Adili <Ri...@xata.com> wrote:
>
>  Hi,
>
> How does one go about logging the outgoing SOAP requests?
>
> Rich Adili
>