http://camel.465427.n5.nabble.com/Updating-datasource-at-runtime-with-camel-sql-td5783374.html
Thank you for all your kind support.
I confirmed that the following method worked fine for me and I decided to use
it.
> you can think of wrapping your datasource which would contain the toggle
>
you can think of wrapping your datasource which would contain the toggle
logic based on your conditions and delegate the call to actual datasource.
the SQL component would get an instance of your datasource.
Regards,
-Yogesh
--
View this message in context:
http://camel.465427.n5.nabble.com/U
am looking forward to your future support as well.
> -Original Message-
> From: Quinn Stevenson [mailto:qu...@pronoia-solutions.com]
> Sent: Friday, June 03, 2016 12:12 AM
> To: users@camel.apache.org
> Cc: 福田 奏
> Subject: Re: Updating datasource at runtime with camel-sql
t; To: users@camel.apache.org
> Cc: 福田 奏
> Subject: Re: Updating datasource at runtime with camel-sql
>
> If you’re willing to use camel-scr or camel-blueprint, you can make this
> happen pretty easily.
>
> You’d expose the data source as a service, and then inject it into the
If you’re willing to use camel-scr or camel-blueprint, you can make this happen
pretty easily.
You’d expose the data source as a service, and then inject it into the route -
the exact method would change based on whether you’re using camel-scr or
camel-blueprint.
If you’re using camel-scr, whe
