In case the answers to my questions are no, considering the serious issue of
having a supposedly empty body suddenly filled with the whole file, I would
then consider the extreme solution of giving up lazy reading (or at least
having it optional, with clear explanations of the consecuencies).
Hi Willem,
thanks for your reply.
The more I think about this, the more I get convinced that this isn't right.
Whatever the case is, the file should be read only once. I cannot find a
scenario where reading the file more than once is different than exploiting
a loose side effect.
Maybe it's
Claus,
I gave it a thought but... if what you say is true, why when the body type
is String then - after the bean call - the body does atually change to null?
It seems to be a problem of consistency or maybe there's a bug in the noop
implementation, I don't know.
Anyway, I debugged the code and
Hi all,
using the file component I encountered a behaviour that doesn't seem right
to me... but maybe it's an intended behaviour.
Basically the issue shows when I have a route that reads the contents of a
file using the file component and then the message body goes to null. At
this point, any
Ok, at the end, I found what my problem was. I'm ashamed to admit, the
problem was between the keyboard and the chair, thus me.
This are the gotchas:
- I created the folder process under inbox, but with the command
copyTo=process I'm actually referring to a folder at the root of the email
folder
Hi all,
I'm going to post a question that has already been posted here
http://camel.465427.n5.nabble.com/Forward-mail-via-camel-td5715953.html
and here
http://camel.465427.n5.nabble.com/Missing-start-boundary-exception-on-camel-mail-2-10-2-td5724769.html
, without resolution. Since the
