Use of Content-Type in JMS Header not in line with JMS specification
--------------------------------------------------------------------
Key: CXF-1805
URL: https://issues.apache.org/jira/browse/CXF-1805
Project: CXF
Issue Type: Bug
Components: Transports
Affects Versions: 2.1.2
Reporter: Seumas Soltysik
Priority: Blocker
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
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
