The multiRef elements are missing.

[Former Member]

hello friends

I'm using the receiver soap adapters for consuming the axis 1.0 web services, in order to do this, i'm using the message types referenced in the wsdl imported.

But, the multiref elements are missing in the response message.

what I must do?

Regards.

Sergio Gómiz

[Former Member]

I found the solution for this issue.

The issue is in the kind of encoding used inside of wsdl.

The kind of enconding = 'encoded' is not supported, because it makes declarations of types with many nodes (href = / multiref).

I used the kind encoding = 'literal', which makes just one node inside xml:body, then it is supported for sap xi.

This way work correctly

I hope to have been helpful

best regards.

[Former Member]

Hi Sergio,

I've got a webservice with some 3rd Party system, and XI cannot process the response to my sent message (the ACK basically) that I have to push to R/3 via proxy. Did you solve this issue at SAP side or at the 3rd Party side??

cheers,

Edu

[Former Member]

Hi sergio,

Good if you got it done , revert back if any more help needed.

Regards

Abhi

[Former Member]

Hi sergio,

The XSDs which you import in the external definitions are a message types omly , thats why if you observe my reply I gave you information for creating the Message Interfaces after taking that Ext Def.

Create the inbound and outbound interfaces as given in my previous reply you will get it right

Regards

Abhi

[Former Member]

Hi Abhi

you say that else import the create an external reference to wsdl, I must create an external definitions for the all response data type, or for the data type (href= #id0) generated into response soap??

Thank you for help me.

Regards

Sergio Gómiz

[Former Member]

HI,

When you imported the wsdl into the IR, dod you make sure that the option "RPC Style" was chosen ?

Thanks,

Renjith

[Former Member]

HI Renjith

it already was choosen "RPC Style", when I imported.

thanks,

Sergio Gómiz

[Former Member]

Hi Sergio,

Is the response a multi-part response? I am not sure whether the soap adapter will take care of multi-part responses....

When you checked the RWM message monitor in adapter engine, was there any attachments other than the payload..in the drop down ?

Thanks,

Renjith

[Former Member]

Renjith

in the above reply, there are the detailed message response.

In the message monitor, not appear any attachments.

do you consuming any axis (release 1 ) web services ever?

Regards.

Sergio

[deviprasad_pothireddy]

Hi Sergio,

save the wsdl file in External definition as XSD category. Then you can see the message types.

reward points if it useful.

Regards,

Deviprasad

[Former Member]

hello Deviprasad !

I already imported the wsdl file like as external definition as WSDL Category Then I reused his message types for making the interface message.

The problem is that not recognizes following response payload (<altaInspeccionReturn href="#id0"/>)...

<?xml version="1.0" encoding="UTF-8"?>

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

<soapenv:Body>

<ns1:altaInspeccionResponse soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="http://mansub.webservice.mansub.gom.com/">

<altaInspeccionReturn href="#id0"/>

</ns1:altaInspeccionResponse>

<multiRef id="id0" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns2:RespuestaOperacion" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns2="urn:ServicioIntegracionMansub">

<codigoError xsi:type="xsd:int">0</codigoError>

<dato xsi:type="xsd:string" xsi:nil="true"/>

<mensaje xsi:type="xsd:string">inspeccion dada de alta</mensaje>

</multiRef>

</soapenv:Body>

</soapenv:Envelope>

In the monitoring adapter (runtime workbench) it appear this payload ...

- <ns1:altaInspeccionResponse xmlns:ns1="http://mansub.webservice.mansub.gom.com/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">

<altaInspeccionReturn href="#id0" />

</ns1:altaInspeccionResponse>

[Former Member]

sergio,

if it is an external defination you dont need to require define Message type.

Regards

Sreeram.g.reddy

[Former Member]

hello Sreeram

I not define Message type, I reused them into interface message.

thanks anyway

Regards.

Sergio Gómiz

[Former Member]

Hi,

and then you can follow the link of consuming the webservice

/people/boris.mohr/blog/2007/01/23/how-to-guide-for-consuming-a-web-service-with-a-standalone-client-using-sap-netweaver-application-server-javatm-ee-5-edition

Hope you will find your answer. Revert back if not

Regards

Abhi

[Former Member]

HI,

Please see the below links

Consuming XI Web Services using Web Dynpro – Part II-/people/riyaz.sayyad/blog/2006/05/08/consuming-xi-web-services-using-web-dynpro-150-part-ii

Consuming XI Web Services using Web Dynpro – Part I -/people/riyaz.sayyad/blog/2006/05/07/consuming-xi-web-services-using-web-dynpro-150-part-i

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/0d7349b6-0901-0010-ddbe-ec43178a...

/people/sap.user72/blog/2006/01/16/xi-propagation-of-meaningful-error-information-to-soap-client

/people/kevin.liu/blog/2006/04/12/wsdl-11-binding-extension-for-soap-12

yes it will be possible, see below links

/people/thomas.jung3/blog/2005/01/11/publishing-abap-webservices-to-an-external-uddi-server

/people/sap.user72/blog/2005/11/17/xi-how-to-publish-wsdl-generated-from-xi-to-uddi

/people/thomas.jung3/blog/2005/05/25/sap-teched-2005--shameless-plug

Troubleshooting SOAP Message - XI - /people/varadharajan.krishnasamy/blog/2007/01/09/troubleshooting-soap-message--xi

Troubleshooting - RFC and SOAP scenarios-/people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009

Regards

Chilla..

[Former Member]

HI Sergio,

While taking the SD from external definitions you will create the outbound and inbound message Interfaces.

Just check first that whether the input message and output message you selected are correct or not .

Every imported message will have two message into it , in... and out...

For outbound Interface

Input message -

---

out...

output message --- in...

for inbound Interface

Input message -

---

in...

output message --- out...

Regards

Abhi