[
https://issues.apache.org/jira/browse/CAMEL-3397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12969265#action_12969265
]
Claus Ibsen commented on CAMEL-3397:
------------------------------------
To leverage all the existing functionally on the consumer side, eg. what should
happen with the file after the exchange has been processed? should it be
deleted, moved, etc.
Then it would most likely to leverage a PollingConsumer for the GET command and
retrieve the file that way. That will use the consumer under the hood.
Then you just check if the Exchange returned is null or not. If null then no
filed existed.
And you will then have to transfer the synchronization from the returned
Exchange to the existing Exchange, as it contains the on completion logic.
See the PollEnrich EIP pattern for similar details.
> Support in-only semantic for file and ftp component
> ---------------------------------------------------
>
> Key: CAMEL-3397
> URL: https://issues.apache.org/jira/browse/CAMEL-3397
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Affects Versions: 2.5.0
> Reporter: Hadrian Zbarcea
> Assignee: Hadrian Zbarcea
> Fix For: 2.6.0
>
>
> Currently we only support in-only for file: and ftp: endpoints, in the sense
> that the content of the message is written to a file and no output gets
> produced.
> It would be useful to support a scenario in which one could send an empty
> message to a file with a GET operation such that the content of the file is
> retrieved as an out instead of written to the file.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
