[
https://issues.apache.org/jira/browse/SYNAPSE-424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12645403#action_12645403
]
irantha suwandarathna commented on SYNAPSE-424:
-----------------------------------------------
Is this configuration support encapsulating a general Swa/MTOM payload into a
JMS message? what if number of attachments for a message is not fixed. Issue is
mapping HTTP headers into other transport headers.
Simply making Axis2 engine assumes a default message conetent-type (text/xml;
charset=utf-8) when content-type is unknown independent of the transport will
resolve majority of issues.
> 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]
