Attachment getting lost after routing through Camel

[soumya banerjee <so...@gmail.com>]

I am trying to route a message based on the content(content based routing)
through the camel component.The message has an attachment of binary
data.When the message is received in the destination the attachment section
of the message is getting lost.

In the source code I found that the JBIBinding.java only copies the message
body and the message headers.Dont know for sure if this is the problem.

I am using a filepoller and file sender as the source and the destination.It
tries to send a binary file through the camel component into a specific
directory.

Are there any solutions to this?

My servicemix version is 3.2.1
-- 
View this message in context: http://www.nabble.com/Attachment-getting-lost-after-routing-through-Camel-tp16245320s12049p16245320.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.

Re: Attachment getting lost after routing through Camel

[Lars Heinemann <la...@compart.net>]

Hi,

actually the attachment support in Camel is not existing at all.
(see http://issues.apache.org/activemq/browse/CAMEL-385)

As it seems to me this issue will be open for a longer time, I would suggest using the message properties for your attachment as a workaround. For this write your own FileMarshaler which will put the attachment in the message properties instead of the body or attachment.

Regards,
Lars




soumya banerjee schrieb:
> I am trying to route a message based on the content(content based routing)
> through the camel component.The message has an attachment of binary
> data.When the message is received in the destination the attachment section
> of the message is getting lost.
>
> In the source code I found that the JBIBinding.java only copies the message
> body and the message headers.Dont know for sure if this is the problem.
>
> I am using a filepoller and file sender as the source and the destination.It
> tries to send a binary file through the camel component into a specific
> directory.
>
> Are there any solutions to this?
>
> My servicemix version is 3.2.1
>