Return-Path: Delivered-To: apmail-camel-dev-archive@www.apache.org Received: (qmail 48247 invoked from network); 27 Sep 2010 06:57:04 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 27 Sep 2010 06:57:04 -0000 Received: (qmail 85951 invoked by uid 500); 27 Sep 2010 06:57:04 -0000 Delivered-To: apmail-camel-dev-archive@camel.apache.org Received: (qmail 85845 invoked by uid 500); 27 Sep 2010 06:57:03 -0000 Mailing-List: contact dev-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@camel.apache.org Delivered-To: mailing list dev@camel.apache.org Received: (qmail 85837 invoked by uid 500); 27 Sep 2010 06:57:02 -0000 Delivered-To: apmail-activemq-camel-dev@activemq.apache.org Received: (qmail 85834 invoked by uid 99); 27 Sep 2010 06:57:02 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Sep 2010 06:57:02 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Sep 2010 06:57:01 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o8R6ueX2026800 for ; Mon, 27 Sep 2010 06:56:41 GMT Message-ID: <323306.33371285570600438.JavaMail.jira@thor> Date: Mon, 27 Sep 2010 02:56:40 -0400 (EDT) From: "Claus Ibsen (JIRA)" To: camel-dev@activemq.apache.org Subject: [jira] Updated: (CAMEL-3163) Add look for mark file feature to file consumer In-Reply-To: <12810739.33361285570480444.JavaMail.jira@thor> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: ae95407df07c98740808b2ef9da0087c [ https://issues.apache.org/activemq/browse/CAMEL-3163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-3163: ------------------------------- Description: Its still common to transfer data using files and using a marker file when the data is ready. We should have a feature on the file consumer, so it can be used to scan for marker files, and then use the real file as the message body. And then when its done it can delete/move both files. The problem is how to define an easy way of correlating the marker file to the real file. We can use an Expression for that. For example maybe something like, (use better option names) {{realFile=${file:name.noext}.csv&include=.*.ready}} Then Camel will react when there is a .ready file in the folder. And evaluate the expression and see if a file with that result exists. When it's done the marker file should be deleted, and the real file should be moved using the existing options for that. was: Its still common to transfer data using files and using a marker file when the data is ready. We should have a feature on the file consumer, so it can be used to scan for marker files, and then use the real file as the message body. And then when its done it can delete/move both files. The problem is how to define an easy way of correlating the marker file to the real file. We can use an Expression for that. For example maybe something like, (use better option names) {{realFile=${file:name.noext}.csv&filter=*.ready}} Then Camel will react when there is a .ready file in the folder. And evaluate the expression and see if a file with that result exists. When it's done the marker file should be deleted, and the real file should be moved using the existing options for that. > Add look for mark file feature to file consumer > ----------------------------------------------- > > Key: CAMEL-3163 > URL: https://issues.apache.org/activemq/browse/CAMEL-3163 > Project: Apache Camel > Issue Type: New Feature > Components: camel-core, camel-ftp > Affects Versions: 2.4.0 > Reporter: Claus Ibsen > Priority: Minor > Fix For: 2.6.0 > > > Its still common to transfer data using files and using a marker file when the data is ready. > We should have a feature on the file consumer, so it can be used to scan for marker files, and then use the real file as the message body. > And then when its done it can delete/move both files. > The problem is how to define an easy way of correlating the marker file to the real file. We can use an Expression for that. > For example maybe something like, (use better option names) > {{realFile=${file:name.noext}.csv&include=.*.ready}} > Then Camel will react when there is a .ready file in the folder. And evaluate the expression and see if a file with that result exists. > When it's done the marker file should be deleted, and the real file should be moved using the existing options for that. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.