SOAP Receiver problem

[inigo_sacramento]

Hi everyone.

I'm facing a new problem with SOAP Receiver adapter.

We have an WSDL that works perfectly using SOAP Clients such as SOAPUI or StylusStudio. End-point is HTTPS://XXXXX:XXX/XXXXX

WSDL is like this :

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

<!-- Call Adapter

-->

<tes:registraEntrada0Request xmlns:tes="http://testing.com" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">

<asu_id>SIO7</asu_id>

<asu_descripcion>desc</asu_descripcion>

<uo_id>1272</uo_id>

<nombre>nombre</nombre>

<ape1>ape1</ape1>

<ape2>ape2</ape2>

<usu_id>virtualdesa</usu_id>

<usu_pass>virtualdesa</usu_pass>

</tes:registraEntrada0Request>

Problem is when i try to use this webservice from XI using a SOAP Receiver communication channel. I get a strange error :

soap fault: No Deserializer found to deserialize a ':asu_id' using encoding style 'null'. [java.lang.IllegalArgumentException]

I don't know if the problem is because HTTPS. All the process has been defined correctly in XI and my doubt is about the configuration of the RECEIVER SOAP or the WSDL structure.

Hope you can help me

Regards,

Inigo.

[Former Member]

Hi Inigo,

See this...

cheers,

Prashanth

[bhavesh_kantilal]

One option, use the TCP gateway tool and monitor the SOAP Payload going out of XI and check if this is what the webservice expects.

/people/stefan.grube/blog/2007/03/29/troubleshooting-soap-http-and-mail-adapter-scenarios-with-tcpgateway

Regards

Bhavesh

[MichalKrawczyk]

hi,

check out response by Ricardo,

maybe you need to fill some attributes in an adapter module like mentioned there

Regards,

michal