[jira] Updated: (SYNAPSE-424) JMS transport uses JMS properties in a way that violates the JMS specifications

["irantha suwandarathna (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SYNAPSE-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

irantha suwandarathna updated SYNAPSE-424:
------------------------------------------

    Attachment: commons_jms.patch

Patch for SYNAPSE-424 and SYNAPSE-478.

Piggybacked "Content-Type" on a property  named "ContentType" when former is 
not available (SYNAPSE-424). Seems ther property errors (SYNAPSE-478) can be ignored.


> JMS transport uses JMS properties in a way that violates the JMS specifications
> -------------------------------------------------------------------------------
>
>                 Key: SYNAPSE-424
>                 URL: https://issues.apache.org/jira/browse/SYNAPSE-424
>             Project: Synapse
>          Issue Type: Bug
>          Components: Transports
>    Affects Versions: 1.2
>         Environment: N/A
>            Reporter: Andreas Veithen
>         Attachments: commons_jms.patch
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org