[SWS-510] AxiomSoapMessageFactory throws IllegalArgument when Content-Type is not set Created: 13/May/09  Updated: 04/May/12  Resolved: 13/May/09

Status: Closed
Project: Spring Web Services
Component/s: Core
Affects Version/s: 1.5.6
Fix Version/s: 1.5.7

Type: Improvement Priority: Blocker
Reporter: Pieter van der Meer Assignee: Arjen Poutsma
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

IBM Wensphere 6.1, MQ (JMS), Oracle


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?

Comment by Arjen Poutsma [ 13/May/09 ]

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).

Comment by Arjen Poutsma [ 04/May/12 ]

Closing old issues

Generated at Wed Nov 21 03:45:06 UTC 2018 using JIRA 7.9.2#79002-sha1:3bb15b68ecd99a30eb364c4c1a393359bcad6278.