Return-Path: 
 <users-return-49741-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 AD23F1161A
	for <apmail-camel-users-archive@www.apache.org>;
 Fri,  4 Jul 2014 09:47:49 +0000 (UTC)
Received: (qmail 78952 invoked by uid 500); 4 Jul 2014 09:47:49 -0000
Delivered-To: apmail-camel-users-archive@camel.apache.org
Received: (qmail 78902 invoked by uid 500); 4 Jul 2014 09:47:49 -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 78886 invoked by uid 99); 4 Jul 2014 09:47:48 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Jul 2014 09:47:48 +0000
X-ASF-Spam-Status: No, hits=2.3 required=5.0
	tests=SPF_SOFTFAIL,URI_HEX
X-Spam-Check-By: apache.org
Received-SPF: softfail (athena.apache.org: transitioning domain of
 nocturnal3d@gmail.com does not designate 216.139.236.26 as permitted sender)
Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Jul 2014 09:47:44 +0000
Received: from [192.168.236.26] (helo=sam.nabble.com)
	by sam.nabble.com with esmtp (Exim 4.72)
	(envelope-from <nocturnal3d@gmail.com>)
	id 1X305T-0004vP-S3
	for users@camel.apache.org; Fri, 04 Jul 2014 02:47:23 -0700
Date: Fri, 4 Jul 2014 02:47:23 -0700 (PDT)
From: nocturnal3d <nocturnal3d@gmail.com>
To: users@camel.apache.org
Message-ID: <1404467243822-5753333.post@n5.nabble.com>
Subject: Extending CamelContext namespace/schema
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org

Hi guys,

I'm using Camel with blueprint, I need to kick off a liquibase script per
CamelContext for property access and this requires some bean instantiations
before the routes bootstrap (I need access to the context to be able to
discover the changelog file inside the context).

Currently I've extended the PropertiesResolver and added database access,
this works fine as I provide the accessor to the
PropertiesComponent/PropertyPlaceholder inside the blueprint.xml file and
processing of properties happens before the routes bootstrap - which is what
I need.

This is what the blueprint entries currently look like:

	...
	...
	<bean id="configDataSource"
class="org.springframework.jdbc.datasource.SimpleDriverDataSource">
		<property name="driverClass" value="org.apache.derby.jdbc.EmbeddedDriver"
/>
		<property name="url"
value="jdbc:derby:target/embedded-configdb;create=true" />
		<property name="username" value="" />
		<property name="password" value="" />
	</bean>


	<bean id="propertiesResolver"
class="com.mycompany.support.camel.DatabasePropertiesResolver">
		<property name="dataSource" ref="configDataSource" />
		<property name="liquibaseConfigFile"
value="com/mycompany/support/camel/db.changelog-master.xml" />
	</bean>

	<camelContext id="testContext"
xmlns="http://camel.apache.org/schema/blueprint">
		<propertyPlaceholder
location="file:src/test/resources/com.mycompany.support.camel.cfg,db:schema:APP:table:SUPPORT"
			ignoreMissingLocation="false" propertiesResolverRef="propertiesResolver"
/>
		<routeBuilder ref="supportRoute" />
	</camelContext>
	...
	...


I would like to make this more 'developer friendly' by possibly extending
the camel namespace and use it like so:

	...
	...
	<bean id="configDataSource"
class="org.springframework.jdbc.datasource.SimpleDriverDataSource">
		<property name="driverClass" value="org.apache.derby.jdbc.EmbeddedDriver"
/>
		<property name="url"
value="jdbc:derby:target/embedded-configdb;create=true" />
		<property name="username" value="" />
		<property name="password" value="" />
	</bean>

	<camelContext id="testContext"
xmlns="http://camel.apache.org/schema/blueprint">
		<myPropertyPlaceholder
location="file:src/test/resources/com.mycompany.support.camel.cfg,db:schema:APP:table:SUPPORT"
			dataSourceRef="configDataSource" 
			liquibaseFile="com/mycompany/support/camel/db.changelog-master.xml"
		/>
		<routeBuilder ref="supportRoute" />
	</camelContext>
	...
	...


Is this possible? Ultimately I need access the the camelContext BEFORE the
routes are realised. If there is a better, cleaner way I'm open for
suggestions.

thank you in advance, Jose.



--
View this message in context: http://camel.465427.n5.nabble.com/Extending-CamelContext-namespace-schema-tp5753333.html
Sent from the Camel - Users mailing list archive at Nabble.com.