Return-Path: Delivered-To: apmail-camel-users-archive@www.apache.org Received: (qmail 14146 invoked from network); 6 Sep 2009 04:16:56 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 6 Sep 2009 04:16:56 -0000 Received: (qmail 65946 invoked by uid 500); 6 Sep 2009 04:16:56 -0000 Delivered-To: apmail-camel-users-archive@camel.apache.org Received: (qmail 65864 invoked by uid 500); 6 Sep 2009 04:16:55 -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 65854 invoked by uid 99); 6 Sep 2009 04:16:54 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 06 Sep 2009 04:16:54 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 06 Sep 2009 04:16:44 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1Mk9At-0000J1-AM for users@camel.apache.org; Sat, 05 Sep 2009 21:16:23 -0700 Message-ID: <25314532.post@talk.nabble.com> Date: Sat, 5 Sep 2009 21:16:23 -0700 (PDT) From: snowbug To: users@camel.apache.org Subject: Re: Use regular spring bean definition style rather than xbean camelContext style In-Reply-To: <4AA21CEF.9080201@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: laji.inbox@gmail.com References: <25305561.post@talk.nabble.com> <4AA21CEF.9080201@gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org Thanks for the reply, do I need to open a ticket to track it? Before it is implemented, is there any alternative way of initialize the camel context with the package scan feature? Alan willem.jiang wrote: > > I think we can add the set methods for the PackageScan. > For the ProducerTemplate, you just need to make sure you inject a right > camel context. > > Willem > > snowbug wrote: >> Hi, >> >> I would like to use regular spring bean definition style ( tag) >> rather >> than the more expressive style to define my camel context >> bean. Is it doable? >> >> The reason: >> - I'd like to be able to let the camel bean "depends-on" another bean I >> defined to control the orders of the initialization for a couple of >> critical >> beans >> - I'd like to use Spring's PropertyPlaceholderConfigure to externalize >> some >> properties that need to be changed by the client engineer, and one of >> these >> variables would be the packageScan of the camel context, as I'd like to >> allow the client engineer to add their packages to be scanned by updating >> the properties file. At present, the document says that Camel does not >> support the Spring PropertyPlaceholderConfigure yet. >> >> So after examining the CamelContextFactoryBean, I've tried something like >> this: >> > class="org.apache.camel.spring.CamelContextFactoryBean"> >> >> >> >> >> >> >> >> >> It won't work because the "packageScan" takes a "PackageScanDefinition" >> class, which has a private List property "packages" that does not have a >> public setter, so I have no way to initialize it. >> >> Another thing is that I don't know how to create a template inside the >> context... should it be created as a separate Spring bean? >> >> Thanks, >> >> >> Alan > > > -- View this message in context: http://www.nabble.com/Use-regular-spring-bean-definition-style-rather-than-xbean-camelContext-style-tp25305561p25314532.html Sent from the Camel - Users mailing list archive at Nabble.com.