You can use the content enricher EIP to enrich the splitted message with the file

http://camel.apache.org/content-enricher.html

But the issue is that this EIP currently does not support specifying a dynamic URI with information from the current exchange. This will be improved in the future.

So what you can do instead, is just to set the message body to the file handle of the file to pickup, for example from a method call, and then use the message translator EIP and invoke the method.

public File pickupFile(String name) {
  return new File(name);
}

Then the only question remains, should you do something with the file after you have successfully processed it? eg should you move or delete the file, or nothing at all? If you have to do something, then you would need to do this manually, for example using java code, to eg delete the file etc.

Hi

I think your design is a bit overkill, and its also being dependent on the Camel API.

For example you could have a java bean with this code

public class FileConsumer {

public String loadFile(String filePath) {
String path = filePath.substring(0, filePath.length()-2);
return new File("input/files/" + path));
}

And then use that in the route

from("file:input")
  .split().tokenize("\n")
    .bean(FileConsumer.class)
    .bean(FileProcessor.class);

But it also depends a bit what you do in the FileProcessor? As with my code you essentially set the message body to a java.io.File handle. Where as with your code, you use the ConsumerTemplate API to poll a message (which happens to be file based).

The latter supports the various options on the file component of Camel, so you automatic can move/delete the file afterwards, where as in the first solution you will have to do this yourself.

Also ideally you should not create a new consumer template all the time. See this FAQ as it also applies for the consumer template

http://camel.apache.org/why-does-camel-use-too-many-threads-with-producertemplate.html