[
https://issues.apache.org/jira/browse/CAMEL-13483?focusedWorklogId=248241&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-248241
]
ASF GitHub Bot logged work on CAMEL-13483:
------------------------------------------
Author: ASF GitHub Bot
Created on: 24/May/19 19:33
Start Date: 24/May/19 19:33
Worklog Time Spent: 10m
Work Description: betoflowv93 commented on pull request #2947:
CAMEL-13483 File Component: Add option to fail startup when not having read
permission on folder
URL: https://github.com/apache/camel/pull/2947
Changes:
-add option startingDirectoryMustHaveAccess (checks read and write
permission)
-add a new test
Your feedback would be appreciated :)
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 248241)
Time Spent: 10m
Remaining Estimate: 0h
> File Component: Add option to fail startup when not having read permission on
> folder
> ------------------------------------------------------------------------------------
>
> Key: CAMEL-13483
> URL: https://issues.apache.org/jira/browse/CAMEL-13483
> Project: Camel
> Issue Type: New Feature
> Affects Versions: 2.22.4
> Reporter: Chris
> Priority: Major
> Fix For: 3.0.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When starting a file consumer you configure a folder to poll.
> When the camel context does not have read access on the folder, there is no
> error (or even warning), that route just starts.
> But when saving files into the folder, they are not picked up and there is no
> further message.
> This issue was raised on stackoverflow:
> [https://stackoverflow.com/questions/55920217/camel-file-consumer-when-folder-is-not-accessible]
>
> Ideally, the file consumer would check at startup if it has access to the
> folder (we should propably check for write access here, but read access could
> also be enough?)
> If the component (/context) does not have the required access to the folder,
> it should throw the error and exit the context (so it isn't started in a
> failure state).
> This option should be disabled by default.
> Also we should think about a way to configure the behavior:
> 1. For what permission should the consumer check (read / read-write)
> 2. What should happen when the permission is not given? (just an error /
> error + stop route / error + stop context)
> As always, we should make this configurable via a custom bean.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
