Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Tue, 26 Jul 2011 14:19:09 +0000 (UTC)
From: "Claus Ibsen (JIRA)" <jira@apache.org>
To: dev@camel.apache.org
Message-ID: 
 <1817400299.7465.1311689949763.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1687397362.7367.1311687309819.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Resolved] (CAMEL-4270) File consumer on completion should
 pre copy file information, in case end user messes with them later on
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CAMEL-4270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-4270.
--------------------------------

    Resolution: Not A Problem

The current logic is fine, the file is being bound to the exchange before its being renamed/deleted.

The end user forgot to close file resources and therefore windows would not move the file when it was done. After fixing this it worked fine.

> File consumer on completion should pre copy file information, in case end user messes with them later on
> --------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-4270
>                 URL: https://issues.apache.org/jira/browse/CAMEL-4270
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 2.9.0
>
>
> See nabble
> http://camel.465427.n5.nabble.com/file-move-option-not-working-when-using-split-tp4616425p4616425.html
> The file consumer uses an on completion to execute the delete/rename strategy after the file has been processed. For that to work it uses the file headers on the exchange. But the end user can in between tamper with those, and thus influence the on completion process. We should guard against this by having the on completion do a pre copy of the information it needs.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira