Hi, there!
 Something wrong because for some reasons RECV.log was not generated in client 
side (just TEST.log and SENT.log).
 Web-service successfully accepts connection and answer right (SENT.log has 
expected data).

ps: soap.buf[] has output content as I saw ((

Regards.





________________________________
From: Sebastian Unger <sebastian.un...@uni-rostock.de>
To: "gsoap@yahoogroups.com" <gsoap@yahoogroups.com>
Sent: Thu, May 27, 2010 12:43:22 PM
Subject: Re: [gsoap] Re: Help with dumping incoming soap message

Hi,

um... what's wrong with those ways? 

However, maybe, this is more suitable for your needs: the struct soap contains 
a member char buf[] which is the send- and receive-buffer. After a client 
invoked a service, I think the response should be inside this buffer. But I'm 
not quite sure - you could give it a try.

Regards,

Sebastian

Am Donnerstag, 27. Mai 2010 schrieb anatoly_pro:
> Thanks, Sebastian!
> I know this way( Any other ideas?
> 
> --- In gsoap@yahoogroups.com<mailto:gsoap%40yahoogroups.com>, Sebastian 
Unger <sebastian.un...@...> wrote:
> > Hi,
> > 
> > afaik, you can use the DEBUG-Compile flag which results in three
> > log-files to be created. One of them contains all the sent messages,
> > another one all the received.
> > 
> > Besides, there is a plugin for that task:
> > http://www.cs.fsu.edu/~engelen/soapdoc2.html#tth_sEc19.36.1
> > 
> > Regards,
> > 
> > Sebastian
> > 
> > Am Donnerstag, 27. Mai 2010 schrieb anatoly_pro:
> > > Please help with dumping incoming message.
> > > 
> > > I've sent custom generated message to server and wish to dump received
> > > soap-message to file, but I don't know how:
> > > 
> > > --------
> > > struct soap soap;
> > > soap_init(&soap);
> > > soap_begin(&soap);
> > > soap_connect( &soap, "http://127.0.0.1:8080";, NULL );
> > > 
> > > soap_begin_send(&soap);
> > > soap_send( &soap, "<?xml... blah blah Soap Envelope </>" );
> > > soap_end_send(&soap);
> > > 
> > > //
> > > // there I wish get raw soap response...
> > > //
> > > --------
> > > 
> > > Thanks.
> 
> 


      

Reply via email to