Return-Path: Delivered-To: apmail-camel-dev-archive@www.apache.org Received: (qmail 66221 invoked from network); 26 Jan 2011 23:11:06 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 26 Jan 2011 23:11:06 -0000 Received: (qmail 78997 invoked by uid 500); 26 Jan 2011 23:11:06 -0000 Delivered-To: apmail-camel-dev-archive@camel.apache.org Received: (qmail 78822 invoked by uid 500); 26 Jan 2011 23:11:05 -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 78811 invoked by uid 500); 26 Jan 2011 23:11:05 -0000 Delivered-To: apmail-activemq-camel-dev@activemq.apache.org Received: (qmail 78808 invoked by uid 99); 26 Jan 2011 23:11:05 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Jan 2011 23:11:05 +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; Wed, 26 Jan 2011 23:11:04 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id p0QNAhCt014923 for ; Wed, 26 Jan 2011 23:10:44 GMT Message-ID: <16709968.227741296083443764.JavaMail.jira@thor> Date: Wed, 26 Jan 2011 18:10:43 -0500 (EST) From: "Ashwin Karpe (JIRA)" To: camel-dev@activemq.apache.org Subject: [jira] Commented: (CAMEL-3575) allow ScheduledRoutePolicy to handle more than one action (start, stop, resume, pause) In-Reply-To: <15381098.113861295638663910.JavaMail.jira@thor> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CAMEL-3575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12987278#action_12987278 ] Ashwin Karpe commented on CAMEL-3575: ------------------------------------- Hi, I am not sure that this is an issue... It is indeed possible to set a start and stop time using a single policy for a given route. The only difference is that it sets two separate triggers to handle the start and stop. Also it seems like the patch is missing unit tests to validate that the patch works... There is indeed a problem in being able to apply multiple policies (policy lists on a given route in CAMEL-3254). I will be working on this over the next few days and will apply a fix for this and CAMEL-3254 in 2.7.0, following the release of 2.6.0 Cheers, Ashwin... P.S: Please hold off on applying the above patch... > allow ScheduledRoutePolicy to handle more than one action (start, stop, resume, pause) > -------------------------------------------------------------------------------------- > > Key: CAMEL-3575 > URL: https://issues.apache.org/jira/browse/CAMEL-3575 > Project: Camel > Issue Type: Improvement > Components: camel-quartz > Affects Versions: 2.6.0 > Reporter: Ricardo Veguilla > Fix For: 2.7.0 > > Attachments: ScheduledRoutePolicy-Patch.diff > > > The current implementation of ScheuledRoutePolicy only supports one type of action (start,stop,resume,pause) for only one route. If, for example, you attempt to configure a CronScheduleRoutePolicy with a routeStartTime and routeStopTime, only the one will by handled because ScheduleRoutePolicy (super-class of CronScheduleRoutePolicy) only store one action and one route in the SchedulerContext: > protected void loadCallbackDataIntoSchedulerContext(Action action, Route route) throws SchedulerException { > getScheduler().getContext().put(SCHEDULED_ACTION, action); > getScheduler().getContext().put(SCHEDULED_ROUTE, route); > } > with the effect of creating two timers (one for startTime, the other for stopTime) that execute the same action (the last call to scheduleRoute). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.