You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Guillaume Nodet (JIRA)" <ji...@apache.org> on 2008/10/07 09:18:52 UTC
[jira] Updated: (SM-1348) Add support for mapping between JBI
NormalizedMessage attachments and Camel Message attachments
[ https://issues.apache.org/activemq/browse/SM-1348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guillaume Nodet updated SM-1348:
--------------------------------
Fix Version/s: servicemix-camel-2008.01
> Add support for mapping between JBI NormalizedMessage attachments and Camel Message attachments
> -----------------------------------------------------------------------------------------------
>
> Key: SM-1348
> URL: https://issues.apache.org/activemq/browse/SM-1348
> Project: ServiceMix
> Issue Type: Improvement
> Components: servicemix-camel
> Affects Versions: 3.3
> Reporter: Marcello Teodori
> Assignee: Gert Vanthienen
> Fix For: 3.2.2, 3.3, servicemix-camel-2008.01
>
> Attachments: patch.diff, patch.diff
>
>
> Following the discussion on CAMEL-385, the new attachment support in Camel 1.4 (currently unreleased) requires modification in the servicemix-camel component to allow a correct bidirectional mapping between attachments in JBI Normalized Messages and Camel Messages.
> Attached to this issue there's a patch file with my implementation, tested with a simple flow from a file:poller (servicemix-file) to a ftp:sender (ftp:sender) connected one to the other through a camel route. The attachment test is done using BinaryFileMarshaler to send a binary file. Unfortunately no JUnit tests are provided as I was not able to understand the existing ones in the servicemix-camel component in order to add the attachment verification.
> The patch requires:
> - upgrading the Camel dependency to 1.4-SNAPSHOT (see SM-1347)
> - upgrading the Spring dependency to 2.5.4 as used by Camel 1.4-SNAPSHOT (see SM-1346)
> I hope it can be useful for anyone trying to pass JBI messages with attachments through a Camel route, and eventually be included in a future version of servicemix.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.