Just a note that Camel 2.4 is no longer supported. So if there is a
bug, we dont fix it and release a patch.


The cannot store error indicate on Windows there is some
FileInputStream that has not been closed, and Windows then refuses to
store/write/move/delete files or whatsoever.

You can usually work around that by using

<route>
<from ...>
<convertBodyTo type="java.lang.String"/>
...

In the top of your route so you load the content into memory, and
avoids any FileInputStream being locked or something.



On Wed, Apr 24, 2013 at 4:26 PM, Nibs <nibha...@gmail.com> wrote:
> I am using camel 2.4
>
>
>
> --
> View this message in context: 
> http://camel.465427.n5.nabble.com/recipientList-not-working-properly-tp5731447p5731455.html
> Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
Claus Ibsen
-----------------
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cib...@redhat.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen

Reply via email to