Web services exposed using jbr-provider do not have proper content-type in response.

Solution Unverified - Updated -

Issue

When exposing a SOAP-based web service using a jbr-provider, some flows return SOAP responses that have a content-type of text/html.

Some of our flows return a content-type of 'text/xml', as expected. Those use a SOAPProcessor, which make a single call to one of your internal JSR-181 webservices.  In that case the esb messages has a particular Content-Type property added to the ESB message, which seems to be required by jbr-provider, to return the message with content type 'text/xml'.
Another one, that doesn't work, has an action which is using a ServiceInvoker to call another flow, after the SOAPProcessor has been invoked. In that case the Content-Type property is not added, and the jbr-provider returns the response to the WS Client with a content-type of 'text/html'.

Environment

  • JBoss SOA-P 5

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.