Re: Question about Exchange properties when using File component
I have reported a ticket about the readLock not none by default problem
On Tue, Apr 17, 2018 at 12:33 PM, Martin Lichtin
> Started using the File component (2.19.5) and seeing exchange properties with prefixed names that don't seem to make sense:
> where "CompletePathAndFilename" is an actual full path to a file that is being picked up by File.
> Should it not just be:
Camel in Action 2: https://www.manning.com/ibsen2