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 stupid, but couldn't the file component simply have an internal property that remembers if the file has been already read or not? Or something alike, that basically leaves the lazy reading in place, but avoids multiple readings of the file? Kind regards, A. -- View this message in context: http://camel.465427.n5.nabble.com/GenericFileMessage-creates-body-from-file-multiples-times-tp5765116p5766473.html Sent from the Camel - Users mailing list archive at Nabble.com.
