invalid content type for SOAP

[Former Member]

Hello,

have this error message here, but seems not really logical to me:

We added an external WSDL to our interface which we call here:

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

- <!--

...

-->

- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">

<SAP:Category>XIAdapterFramework</SAP:Category>

<SAP:Code area="MESSAGE">GENERAL</SAP:Code>

<SAP:P1 />

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: java.io.IOException: invalid content type for SOAP: TEXT/HTML</SAP:AdditionalText>

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack />

<SAP:Retry>M</SAP:Retry>

</SAP:Error>

Is there possibly something wrong with the WSDL? Everything is accepted in Repository when activating!

Best regards

Dirk

[Shabarish_Nair · Accepted solution]

Just have a look at this blog and do confirm

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

Also note if you need to configure any proxy authentication for your network.

[bhavesh_kantilal]

Dirk,

Is the SOAP url and SOAP action in the SOAP adapter correct?

Also, are you using DO NOT USE SOAP ENVELOPE?

Regards,

Bhavesh

[Former Member]

Hi Bhavesh,

yes, SOAP url is fine. SOAP action is the method name from WSDL (learned from Michal), so ok too!

At the moment the entry for "Do not use soap envelope" is not set.

Will do this and retry, but, what is the effect of this for the web service?

regards

Dirk

[bhavesh_kantilal]

Dirk,

<i>At the moment the entry for "Do not use soap envelope" is not set.

Will do this and retry, but, what is the effect of this for the web service?</i>

Do not use this. This is used if you need to manually create SOAP envelope.

Take a look at the blog - Troubleshooting RFC and SOAP scenarios by Shabrish for SOAP url and SOAP action.

Regards,

Bhavesh

[Former Member]

Hello,

Thank you for your ideas and links!

We have found the problem. It was something different.

We imported the WSDL, but somebody made changes before in the namespaces.

A colleague has mentioned this. We deleted the WSDL and imported the original one.

Now it is fine!

(Sometimes I think we need a special control system to know who did what!)

But nevertheless my posting was not useless because you gave me some more input I will need in the future, I am sure because our SOAP process is not completed yet as there are some more mehtods we have to use.

Best regards

Dirk