Return-Path: X-Original-To: apmail-camel-users-archive@www.apache.org Delivered-To: apmail-camel-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 35E5ADEAF for ; Mon, 4 Mar 2013 20:35:14 +0000 (UTC) Received: (qmail 2411 invoked by uid 500); 4 Mar 2013 20:35:13 -0000 Delivered-To: apmail-camel-users-archive@camel.apache.org Received: (qmail 2377 invoked by uid 500); 4 Mar 2013 20:35:13 -0000 Mailing-List: contact users-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@camel.apache.org Delivered-To: mailing list users@camel.apache.org Received: (qmail 2368 invoked by uid 99); 4 Mar 2013 20:35:13 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Mar 2013 20:35:13 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of cwolf.algo@gmail.com designates 209.85.128.177 as permitted sender) Received: from [209.85.128.177] (HELO mail-ve0-f177.google.com) (209.85.128.177) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Mar 2013 20:35:08 +0000 Received: by mail-ve0-f177.google.com with SMTP id m1so5119072ves.36 for ; Mon, 04 Mar 2013 12:34:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=aHO2us1Jsf0FCZ2OH6i22L389/3IIYtCyRvkfHnHl3U=; b=YWA5n9tbd/4pK4e+ZTYJL4wZG+AX6a9rY+7ypYpCsV319KJ1JoUxCB7vGVHvXHWd+8 ZZfT6zkXiMe8GCOiaqGy5fJwtLMVA07qyy9teHNauDTxGN/3bBrYCU15o4YImnWDMwTp g9zydSZ5OU2vflxVPyCxxtMU2i9OCMLPv/B2wXbbVPc3i0KmmEolsvgz52F4Lf/ZWXV/ XVxMcf0irC+2gIfKdGnhvcFeQlx+Efi64NoMlHbAexx6WCTY4ywSoYMV5R+pHyuNPMcW Mu58EkX0RZIk9WZ1broWNpek1hsr/JI9hpTSKQQNK78PSAQx2Qgsy9P9rIJiD1r1uiQE SxRw== MIME-Version: 1.0 X-Received: by 10.52.36.234 with SMTP id t10mr7373411vdj.95.1362429287494; Mon, 04 Mar 2013 12:34:47 -0800 (PST) Received: by 10.58.221.8 with HTTP; Mon, 4 Mar 2013 12:34:47 -0800 (PST) In-Reply-To: References: Date: Mon, 4 Mar 2013 15:34:47 -0500 Message-ID: Subject: Re: How to schedule FTP with quartz? From: Chris Wolf To: users@camel.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org Ok, that's what I was looking for - specifically the Cron version: http://camel.apache.org/cronscheduledroutepolicy.html Thanks for the help, Chris On Sat, Mar 2, 2013 at 1:43 AM, Claus Ibsen wrote: > Hi > > See about route policy > http://camel.apache.org/routepolicy > > And the scheduled route policy > http://camel.apache.org/scheduledroutepolicy.html > > On Sat, Mar 2, 2013 at 12:15 AM, Chris Wolf wrote: >> I have a requirement to download files via FTP during a certain time >> window and according to a schedule. e.g. Only on trading days between >> 6:30AM and 7:00AM. The FTP component, alone, seems to just do >> indefinite polling according to delay/initialDelay. >> >> From the "Camel In Action" book, chapter 7, I see some examples of >> sending a text message with the Timer and Quartz components, but I >> can't quite see how to put that together to implement "kicking off >> routes at specified intervals", mentioned in the best practices list >> at the end of that chapter. How would I use quartz to stop/start the >> FTP component, or the route that it's in? >> >> Thanks, >> >> Chris > > > > -- > Claus Ibsen > ----------------- > Red Hat, Inc. > FuseSource is now part of Red Hat > Email: cibsen@redhat.com > Web: http://fusesource.com > Twitter: davsclaus > Blog: http://davsclaus.com > Author of Camel in Action: http://www.manning.com/ibsen