[SYNAPSE-424] JMS transport uses JMS properties in a way that violates the JMS specifications

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.2
• Fix Version/s: 2.0
• Component/s: Transports
• Environment: N/A
• Assignee: Andreas Veithen
• Reporter: Andreas Veithen
• Created: 11/Aug/08 20:03
• Updated: 30/Aug/09 15:38
• Resolved: 09/Nov/08 17:17

Description

According to section 3.5.1 of the JMS specification (version 1.1), "Property names must obey the rules for a message selector identifier." According to section 3.8.1.1 on selectors, "An identifier is an unlimited-length character sequence that must begin with a Java identifier start character; all following characters must be Java identifier part characters." The JMS transport's use of a property named "Content-Type" is in violation of this specification.

Note that some JMS providers (such as qpid) accept illegal identifiers while others (such as WebSphere's SIBus client) don't.

Issue Links

• is duplicated by: WSCOMMONS-499 Invalid message property name "Content-Type" in JMSSender
• relates to: SYNAPSE-478 Synapse exceptions with JBossMQ