Its much easier to just set delay=30m on the file endpoint and not use the cron route policy.
maybe but the question here is why i have this weired behavior using the CronScheduledRoutePolicy ? Moreover, using the delay option maybe a solution for one case but when about any advanced job whose execution depends on a certain time or day?
the problem here is that any cron expression is ignored and i don't really get the main reason for that.
Anyone from the Fuse team to help us solve this issue please?
You misunderstand the file component.
The file component has its own scheduling so it will keep picking up files as long as it runs. It has a default timer that runs every 500 milli seconds.
So even if you use the cron route policy, to start the route. Then you have not told it when to stop the route. So what you do with the cron is just to start the route every 30 minutes. But the route is already started. And the file component will as said by default keep running and pickup new files every 500 milli seconds.
So again its much easier to just tell the file component to use a 30 minute delay.
If not you would need to have a stop cron expression also.
ok i got it !
but what are the other components with their own scheduling ? is there any documentation about that ? ( did not find any)