Skip to Content
avatar image
Former Member

DeliveryException: invalid content type for SOAP: TEXT/HTML

My scenario is RFC -> XI -> SOAP (synchronous), but when I test this scenario, I got the error message "DeliveryException: invalid content type for SOAP: TEXT/HTML", I search the document and change it following this blog: /people/varadharajan.krishnasamy/blog/2007/01/09/troubleshooting-soap-message--xi

1. I add a MessageTransformBean module before the original one

2. I add a transform key, the value is text/html;charset=utf-8

But when I active this channel and test again, I got another message:

XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION-HTTP 400 Bad Request.

I only find one discussion about it but I still have no idea how to solve the problem. Do I need to change my mapping ? And when field should I generated in the mapping?

Problem with SOAP receiver adapter

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Aug 22, 2007 at 08:26 AM

    > 2. I add a transform key, the value is

    > text/html;charset=utf-8

    In a SOAP call this value <b>must not</b> be text/html.

    Always choose <b>text/xml</b>

    Regards

    Stefan

    Add comment
    10|10000 characters needed characters exceeded

  • Aug 23, 2007 at 10:16 AM

    When you have this error message, there are mainly two reasons:

    1. The URL is not correct/complete -> Open this URL in your browser. Maybe you need a firewall proxy?

    2. The user/password is not correct.

    Regards

    Stefan

    Add comment
    10|10000 characters needed characters exceeded

    • And of course you have also applied the correct SOAPAction.

      Sorry for bothering you, but is difficult to guess the error, but in my experience, must issues are due to wrong configuration.

      Could you check with TCPGateway, what error is sent back?

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

      Regards

      Stefan