[CXF-1805] Use of Content-Type in JMS Header not in line with JMS specification

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 2.1.2
• Fix Version/s: 2.0.9, 2.1.3
• Component/s: Transports
• Assignee: Ulhas Bhole
• Reporter: Seumas Soltysik
• Created: 17/Sep/08 21:44
• Updated: 23/Jan/09 17:52
• Resolved: 18/Sep/08 17:22

Description

It looks like the use of "Content-Type" as a JMS header property is illegal.

When using the JMS transport with Weblogic, I got the following error:

Caused by: java.io.IOException: weblogic.jms.common.MessageFormatException: Illegal property name, 'Content-Type'
at org.apache.cxf.transport.jms.JMSConduit$JMSOutputStream.doClose(JMSConduit.java:263)
at org.apache.cxf.io.CachedOutputStream.close(CachedOutputStream.java:167)
at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:66)

After doing some googling I found this: http://www.nabble.com/-jira--Created:-(SYNAPSE-424)-JMS-transport-uses-JMS-properties-in-a-way-that-violates-the-JMS-specifications-td18932701.html

Dan K also pointed out the following: The SOAP over JMS spec uses the header name: SOAPJMS_contentType