On 17 May 2013, at 09:33, Claus Ibsen wrote:
> You can use the move option on the Camel file consumer, and then use a
> bean to calculate the file name. http://camel.apache.org/file2
Claus, by the way, your comment let to an 'aha' moment - the kind that Manning
talk about :)
Being new to Camel,
Ah, cool - thanks. That's much less code than a custom component, endpoint and
producer.
I discounted the 'move' option, because the default behaviour seemed to be to
move the existing files to make room for the duplicate, instead of picking a
different name for the duplicate.
Peter
On 17 Ma
Component())
5. Change my file:// URIs to archive:// URIs to use my new component.
Peter
On 16 May 2013, at 12:23, Peter Hilton wrote:
> I’m using Camel to process files, and need to save a copy of each incoming
> file to an 'archive' directory. In addition, if another file arri
On 16 May 2013, at 12:23, Peter Hilton wrote:
> I’m using Camel to process files, and need to save a copy of each incoming
> file to an 'archive' directory. In addition, if another file arrives with the
> same name as an earlier file, I must add this to the archive with a dif
I’m using Camel to process files, and need to save a copy of each incoming file
to an 'archive' directory. In addition, if another file arrives with the same
name as an earlier file, I must add this to the archive with a different file
name and not overwrite an existing archive file.
Two questi
On 14 May 2013, at 18:10, Peter Hilton wrote:
> I have a route that takes a file, parses it and then sends JSON to a web
> service. If the Camel processor that parses the file throws a parse
> exception, the configured error handler moves the file to the dead letter
> endpoint. Thi
On 14 May 2013, at 18:10, Peter Hilton wrote:
> …
>
> val deadLetterErrorHandler =
> deadLetterChannel(failureEndpoint).disableRedelivery()
> deadLetterErrorHandler.setFailureProcessor(ErrorProcessor())
> errorHandler(deadLetterErrorHandler)
>
How should I approach the following scenario? I’m starting to suspect that I'm
doing it wrong…
I'm using: Camel 2.11.0, Scala DSL, Scala 2.10.0, sbt 0.12.2, JDK 1.6.0_43, OSX
10.8.3
I have a route that takes a file, parses it and then sends JSON to a web
service. If the Camel processor that p
