AxiomSoapMessageFactory throws IllegalArgument when Content-Type is not set [SWS-510]

[gregturn]

Pieter van der Meer opened SWS-510 and commented

Messages recieved must contain the header "Content-Type" when the header does not contain this a IllegalArgument exceptions is thrown, "TransportInputStream contains no Content-Type header".
Though this is correct is the pure sense, there is no real specification for sending messages by means of MOM.

When the sender of the message is Spring-WS this does not impose any problems (the header is set) but when others, in our case Oracle BPM, sends a message the header is not send and where not able to process the response.

Possible solution, assume a default value for the "Content-Type" header is message from the MOM. content-type=text/xml?

---

Affects: 1.5.6

Referenced from: commits 5018157, 378cf9b

[gregturn]

Arjen Poutsma commented

Actually, there is a proposed specification for running SOAP over JMS, see http://www.w3.org/TR/2008/WD-soapjms-20081121/, and Spring-WS is among the few implementations (if not the only one): we use the SOAPJMS_contentType JMS property as value for the Content-Type header. This just shows that implementing a spec does not guarantee interoperability, I guess.

So I will make the Content-Type optional, and default to the standard SOAP 1.1 content-type (text/xml).

[gregturn]

Arjen Poutsma commented

Closing old issues