Return-Path: 
 <users-return-35721-apmail-camel-users-archive=camel.apache.org@camel.apache.org>
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 749E8ED15
	for <apmail-camel-users-archive@www.apache.org>;
 Thu, 17 Jan 2013 20:35:28 +0000 (UTC)
Received: (qmail 79574 invoked by uid 500); 17 Jan 2013 20:35:28 -0000
Delivered-To: apmail-camel-users-archive@camel.apache.org
Received: (qmail 79541 invoked by uid 500); 17 Jan 2013 20:35:27 -0000
Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@camel.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@camel.apache.org>
List-Post: <mailto:users@camel.apache.org>
List-Id: <users.camel.apache.org>
Reply-To: users@camel.apache.org
Delivered-To: mailing list users@camel.apache.org
Received: (qmail 79533 invoked by uid 99); 17 Jan 2013 20:35:27 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Jan 2013 20:35:27 +0000
X-ASF-Spam-Status: No, hits=2.0 required=5.0
	tests=SPF_NEUTRAL,URI_HEX
X-Spam-Check-By: apache.org
Received-SPF: neutral (nike.apache.org: 216.139.250.139 is neither permitted
 nor denied by domain of flipdeskript@googlemail.com)
Received: from [216.139.250.139] (HELO joe.nabble.com) (216.139.250.139)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Jan 2013 20:35:20 +0000
Received: from sam.nabble.com ([192.168.236.26])
	by joe.nabble.com with esmtp (Exim 4.72)
	(envelope-from <flipdeskript@googlemail.com>)
	id 1TvwAt-0006Gu-QG
	for users@camel.apache.org; Thu, 17 Jan 2013 12:34:59 -0800
Date: Thu, 17 Jan 2013 12:34:59 -0800 (PST)
From: Hude <flipdeskript@googlemail.com>
To: users@camel.apache.org
Message-ID: <1358454899781-5725719.post@n5.nabble.com>
In-Reply-To: <1358367435548-5725660.post@n5.nabble.com>
References: <1354872857576-5723760.post@n5.nabble.com>
 <1358367435548-5725660.post@n5.nabble.com>
Subject: Re: Camel QuartzComponent failed on recreating endpoint
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org

Hello,

no not really. We've changed our routes from quartz to direct. Also we've
created a CamelTriggerJob Bean. This Bean extends QuartzJobBean and has an
Producer which triggeres the direct routes.

For example:

   <bean id=3D"terminTrigger"
class=3D"org.springframework.scheduling.quartz.CronTriggerBean">
       <property name=3D"jobDetail" ref=3D"quartzJob" />
       <property name=3D"cronExpression" value=3D"${a.schedule}"  />
   </bean>

   <bean name=3D"quartzJob"
class=3D"org.springframework.scheduling.quartz.JobDetailBean">
       <property name=3D"jobClass" value=3D"...quartz.CamelTriggerJob" />
       <property name=3D"jobDataAsMap">
           <map>
               <entry key=3D"endpoint" value=3D"direct:termine" />
               <entry key=3D"camelContext" value-ref=3D"camelContext" />
           </map>
       </property>
   </bean>



--
View this message in context: http://camel.465427.n5.nabble.com/Camel-QuartzComponent-failed-on-recreating-endpoint-tp5723760p5725719.html
Sent from the Camel - Users mailing list archive at Nabble.com.