Hey guys,
Thanks a lot for your help. So by reading the file2 documentation
instead of the file documentation, I was able to solve my problem by
adding
doneFileName=${file:name.noext}.done
to the uri for the file being written and also to the uri of the route
that was attempting the subsequent r
That's the old file component, have a look at file2.
http://camel.apache.org/file2.html
> On 05 Nov 2013, at 20:36, Ben Hood <0x6e6...@gmail.com> wrote:
>
> Hey Claus,
>
> Having to acquire a lock on the file sounds like a good way to implement the
> "don't start attempting to read an empty fil
Hey Claus,
Having to acquire a lock on the file sounds like a good way to implement the
"don't start attempting to read an empty file" semantics I'm looking for.
Having said that, the documentation on read locks is somewhat misleading. It
notes a boolean URI parameter called consumer.exclusiveR
If you are talking about how to not pickup new files in a Camel from
route, then take a look at the various read lock documentation on the
file component.
On Tue, Nov 5, 2013 at 2:39 PM, Ben Hood <0x6e6...@gmail.com> wrote:
> Hi,
>
> In my first attempt to use Camel I’ve run into a intra-route tim
