You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by "Asankha C. Perera (JIRA)" <ji...@apache.org> on 2008/11/05 13:09:44 UTC
[jira] Commented: (SYNAPSE-424) JMS transport uses JMS properties
in a way that violates the JMS specifications
[ https://issues.apache.org/jira/browse/SYNAPSE-424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12645202#action_12645202 ]
Asankha C. Perera commented on SYNAPSE-424:
-------------------------------------------
Its better to link SYNAPSE-478 to this issue, thus uploading a patch to one issue will be sufficient, to minimize duplication
> 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