Skip to Content
0
Former Member
Sep 13, 2007 at 01:30 PM

consuming Webservice

20 Views

Hello,

<u>Level</u> : CRM 5.0, WebAS 700.

<u>Situation</u> : Consuming a WebService (using client provided WSDL, we have created the Client Proxy and corresponding logical port).

<u>Problem</u>: The client uses <b>Delphi</b> to generate the WSDL/XML and therefore, some tags do not seem to be supported between <b>SAP</b> and <b>Delphi</b> resulting in <u>SOAP errors</u> (<i>I can give the error later if need be</i>).

<u>For example, Delphi uses</u> :

<message name="AthenaReqAstreinteInit0Request">

<part name="Req" <b><i>type</i></b>="ns1:TAthIAReq"/>

</message>

<u>Whereas SAP requires</u> :

<message name="AthenaReqAstreinteInit0Request">

<part name="Req" <b><i>element</i></b>="ns1:TAthIAReq"/>

</message>

<u>Note</u> : <i>To import the client WSDL (and thus to create the web proxy), I of course changed the occurences of "<u>type</u>" to "<u>element</u>"... in testing, send is OK, receive comes back with SOAP error I think as a result of the tag change I did.</i>

<u>Questions</u> : Can anybody give me suggestions or solutions general as to how we can get around this? Do there exist any "Delphi plug-in" so that our SOAP and XML tags understand each other, etc..??

Thanks,

Tim