Add support for mapping between JBI NormalizedMessage attachments and Camel Message attachments

• Key: SM-1348
• Type: Improvement
• Status: Resolved
• Resolution: Fixed
• Priority: Major
• Assignee: Gert Vanthienen
• Reporter: Marcello Teodori
• Component/s: servicemix-camel
• Affects Version/s: 3.3
• Fix Version/s: 3.3, 3.2.2

Description

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.

Comments

[Marcello Teodori]

Upgraded patch for API change in Camel Endpoint (i.e. getContext becomes getCamelContex)

[Marcello Teodori]

upgraded patch to integrate changes from SM-1373 and latest changes in camel 1.4-SNAPSHOT

[Marcello Teodori]

upgraded patch after components projects split

[Gert Vanthienen]

Patch applied with thanks!

Fixed for components in http://svn.eu.apache.org/viewvc?view=rev&revision=675254
Backported the fix to SMX 3.2.2 in http://svn.eu.apache.org/viewvc?view=rev&revision=675262