[
https://issues.apache.org/jira/browse/SYNAPSE-424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12645665#action_12645665
]
Andreas Veithen commented on SYNAPSE-424:
-----------------------------------------
There is always an exception to the rule :-)
BTW, that reminds me of something: I think that the JMS transport actually may
expose credentials in the EPR! If I remember well, some time ago there was a
modification to expose all JNDI properties in the EPR and I think the
credentials are not filtered out. To be confirmed.
> 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
