[
https://issues.apache.org/activemq/browse/CAMEL-255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Strachan resolved CAMEL-255.
----------------------------------
Resolution: Fixed
Fix Version/s: 1.3.0
Patch applied with thanks!
> Way to send JMS MapMessage and ByteMessage from JMS component
> -------------------------------------------------------------
>
> Key: CAMEL-255
> URL: https://issues.apache.org/activemq/browse/CAMEL-255
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-jms
> Reporter: Roman Kalukiewicz
> Fix For: 1.3.0
>
> Attachments: jms-binding.patch
>
>
> Current JMSBinding doesn't allow to send JMS ByteMessage and MapMessage.
> Natural behavior would be to send those messages if body contains byte[] and
> Map. Now if you want those messages to be sent you have to create them
> yourself, that cannot be done easily as messages require JMS session to be
> created.
> Patch applied represents {{BytesMessage}}s as {{byte[]}} body.
> Moreover when {{byte[]}} body arrives it is sent as {{BytesMessage}}. When
> {{Map}} body arrives it tries to create {{MapMessage}} -- if it cannot be
> created (for example because map elements are not primitives) then if falls
> back to previous behaviour - creates {{ObjectMessage}}.
> It means that JMS component is now symmetric -- if {{BytesMessage}} is
> received then it is sent as {{BytesMessage}}. If {{MapMessage}} is received
> then {{MapMessage}} is sent.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
