SOAP CXF Multipart JMS Message format does not correspond to standard, regression against 6.0.0

Solution In Progress - Updated -

Issue

Our external client has a problem reading a multipart jms soap over jms message.
The problem was fixed in JBossFuse 6.0.0 through JIRA SF-481.

currently we see:

</soapenv:Envelope>
--uuid:dcc04de5-da07-48d8-8469-0cb02b22f299
Content-Type: application/octet-stream
Content-Transfer-Encoding: binary
Content-ID: <attachment>

But according to the spec we would expect a CR/LF between normal body and the next part:

</soapenv:Envelope>

--uuid:dcc04de5-da07-48d8-8469-0cb02b22f299
Content-Type: application/octet-stream
Content-Transfer-Encoding: binary
Content-ID: <attachment>

Environment

  • JBoss Fuse
    • 6.1

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.