dynamic input/output folder location in Camel's file component

Question

As per https://camel.apache.org/file2.html, file component cannot be configured with dynamic input/output folder locations?

Is there any workaround/alternative for the same?

Thanks.

Regards Senthil Kumar Sekar

Output folder location could be dynamic using recipientlist (http://camel.apache.org/how-do-i-use-dynamic-uri-in-to.html) — Mashrur, Aug 14 '15 at 02:48
similar post with solution: http://stackoverflow.com/a/32655201/3784642 — Bernard Hauzeur, Sep 05 '16 at 15:05
A solution for dynamic URIs in from() is explained in http://stackoverflow.com/questions/32368961/how-to-use-a-dynamic-uri-in-from — Bernard Hauzeur, Sep 05 '16 at 15:25
similar question to http://stackoverflow.com/questions/32368961/how-to-use-a-dynamic-uri-in-from — Bernard Hauzeur, Sep 05 '16 at 15:26

score 3 · Answer 1 · answered Mar 12 '14 at 07:53

3

For the file consumer

You can use a customer filter as dynamic selection of which directories/files to pickup. But the starting directory is configured once (hardcoded).

For that to change you would need to stop the route, and change the directory, and start the route again - if you want to attempt that direction.

For the file producer

The file name is fully dynamic you can just set a name as the file header you want. See documentation for details.

answered Mar 12 '14 at 07:53

Claus Ibsen

56,060
7
50
65

1

OP wanted a dynamic output *folder* location; only the `fileName` portion of a file endpoint can be dynamic AFAICT. – pimlottc Jan 13 '15 at 00:21
Beware that if you build dynamic URIs with the CAMEL FTP/SFTP/FTPS component (v2.16.3, likely other versions) you MUST ensure that all variable parts of the URI are passed as Header properties and not URI options; your URI must be the exactly same (ok with ${} props) with every sending. Indeed, a Dynamic Endpoint is recorded in the Cache for every transmission and if the URI differs by a single char, a new object is allocated. This bug https://issues.apache.org/jira/browse/CAMEL-10281 will explode your heap, the documented cache limit (default 1000) is not enforced. – Bernard Hauzeur Sep 05 '16 at 15:18
I wish the comment @berhauz made was in the docs... – Snekse Nov 17 '22 at 17:48

score 1 · Answer 2 · edited Apr 05 '16 at 16:17

1

You can use the header CamelFileName also to dynamically set a directory. Slashes will be turned into directories.

Example: CamelFileName = "directory/dyn_subdirectory_n/myfilename.txt" will be placed into the directory "dyn_subdirectory_n" located in "directory". The filename will be "myfilename.txt".

edited Apr 05 '16 at 16:17

Haroldo Gondim

7,725
9
43
62

answered Apr 05 '16 at 15:16

moritz.vieli

1,747
1
14
17

dynamic input/output folder location in Camel's file component

2 Answers2