The following pipeline does not return HTTP content type, even though it is set by the web service invoked by SOAPProcessor:

HTTP Gateway Listener -> SOAP Processor -> invm service invocation -> inVM Listener -> JAX-WS HTTP Client Action -> Web Service

This severely affects the customer as they wish to call the ESB from .NET, without the content-type header .NET breaks.

Please see Enterprise BZ 826536 for an attached reproducer.