Re: SOAP Request is repeated in the SOAP response.

that's great news, glad you got it.
a good show of patience and persistence!
Jay

MeAgin wrote:
Hi all,

I found the solution for this. This can be configured in our WSDL files.

Here is what you guys will have to do,

1.. Locate the area where your method is described in the WSDL file. If
your method is MyMethod you will get 2 method descriptions for the Request
and the Response. The names would be,
1.. Mymethod
2.. MyMethodResponse
2.. Against the MyMethodResponse all parameters returned will be listed.
This list will contain all parameters from the Mymethod and an additional
parameter with the name Result. Excluding Result parameter delete all other
parameters.
3.. Search your method further down and you will find areas the operations
are described. This tag will start as Operation and the name attribute will
contain your method name.
Ex: <operation name='MyMethod'>

4.. This will contain 2 sub levels Input and Output. You will have to
change the details of the Output tag. All the parameters will be described
against the Part attribute in this tag. Excluding Result remove all other
parameter names.
5.. Now your method will return only the return value of called method not
the parameters passed to the Request.
Like this way you guys can control the values returned in the SOAP response.

Please note I'm using VFP XML web services publisher to generate all these
WSDL files using my COM+ application.

Hope this will help.

Best regards,
Nadee



"MeAgin" <MeAgain@xxxxxxxxx> wrote in message
news:#0FcZiS4GHA.3364@xxxxxxxxxxxxxxxxxxxxxxx
Hi all,

After analyzing WSDL files identified that for the description of the
Response all the parameters of the Request are described with the
additional
parameter "Result". This "Result" will contain the return value from the
called method and the other parameters will contain the values available
when returning. So if we don't make any change in the called method the
parameters will be returned as it is to the client side.

Is there a way to restrict these parameters returned from the server?



Any help is greatly appreciated.



Best regards,

Nadee


"MeAgin" <MeAgain@xxxxxxxxx> wrote in message
news:#tmTN$J3GHA.4632@xxxxxxxxxxxxxxxxxxxxxxx
Hi again,



I found how this is happening but can't figure out why it is happening.

This happens if the parameter values I passed from the client side is
still
available in the parameters I received them on the server when
returning.
For example:



Client side method SaveMail() calls Server side SetMail().

Parameters would be cSessionKey and cXML to the server side method. The
server side method would be like,



Function SetMail

Lpara cSessionKey, cXML

** Some Processing

Return cSavedMailXML

EndFunc



When you return as shown above values available for cSessionKey, cXML
will
be sent in the SOAP message back to the client. The structure of the
SOAP
sent to the client would be something like,



<SOAP-Envelope>

<SOAP header info>

</SOAP header info>

<Result>

=Value of cSavedMailXML

</Result>

<cSessionKey>

=Value of cSessionKey

</cSessionKey>

<cXML>

=Value of cXML

</cXML>

</SOAP-Envelope>



So in my case if I don't change the values of cSessionKey, cXML they
will
be
returned back to the client. I am not sure why this is happening. Is it
some kind a feature or a bug?



As a workaround we can blank out the parameters so they won't be
returned
to
the client. But this is not a standard in VFP. Ie, we don't have to
blank
out parameters at the end of a method. As we received them as LPARA I
assume
those will be released at the end of the method.

Is there a way to overcome this problem?



Best regards,

Nadee




"MeAgin" <MeAgain@xxxxxxxxx> wrote in message
news:O0d4pAJ3GHA.2196@xxxxxxxxxxxxxxxxxxxxxxx
Hi all,



I'm using SOAP tool kit version 3 in my VFP 9 application.



When analyzed SOAP responses closely using the Fiddler I noticed that
the
data we sent (a XML in this case) is again repeated in the response.
Ie,
the
same data we sent to the server is returned back to the client again.



My response from the server is sent within a <Result> tags and after
that
all the detail I sent to the server is returned back again. These
values
will not be received back to your calling method but will be
transferred
from the server to the client. You can check this by using a HTTP
debugger
proxy such as Fiddler.



Is this the behavior of SOAP or can we configure SOAP not to do this?
Why
is it returning the same data we sent back again?



In my case I send a XML to the server and after doing dome processing
receive a XML. Now it seems in the response I have to spend time to
transfer
the original request back! This is very inefficient.



Please advice if this can overcome in any way.





Best regards,

Nadee






.

Relevant Pages

  • Re: SOAP Request is repeated in the SOAP response.
    ... This can be configured in our WSDL files. ... Client side method SaveMailcalls Server side SetMail. ... Parameters would be cSessionKey and cXML to the server side method. ...
    (microsoft.public.fox.helpwanted)
  • Re: SOAP Request is repeated in the SOAP response.
    ... Response all the parameters of the Request are described with the additional ... Client side method SaveMailcalls Server side SetMail. ... Parameters would be cSessionKey and cXML to the server side method. ... The structure of the SOAP ...
    (microsoft.public.fox.helpwanted)
  • Re: SOAP Request is repeated in the SOAP response.
    ... Client side method SaveMailcalls Server side SetMail. ... Parameters would be cSessionKey and cXML to the server side method. ... The structure of the SOAP ...
    (microsoft.public.fox.helpwanted)
  • Re: Starting with SOAP
    ... It has been suggested that SOAP would work for this. ... update some database that the script accesses? ... or the SOAP server? ... I built a form for a client, who now wants to take that data and pass it to another server so it can be used to update a page there. ...
    (comp.lang.perl.misc)
  • Re: VisualWorks as DLL
    ... Windows is WebServices i.e. SOAP. ... Both client and server ... That seems to only allow C to call Smalltalk ... little C wrapper for the existing MetaEdit+ API, so both SOAP and DLLs ...
    (comp.lang.smalltalk)