.n5.nabble.com/Dynamic-datasource-with-Camel-2-15-x-tp5772178p5772598.html
Sent from the Camel - Users mailing list archive at Nabble.com.
dataSource.setUsername("XYZ");
dataSource.setUPassword("XYZ");
?dataSource=#myDataSource
--
View this message in context:
http://camel.465427.n5.nabble.com/Dynamic-datasource-with-Camel-2-15-x-tp5772178p5772328.html
Sent from the Camel - Users mailing list archive at Nabble.com.
egistry(ApplicationContextRegistry.class);
> DataSource dataSource = registry.lookup("dataSource", DataSource.class);
> dataSource.setUrl("XYZ");
> dataSource.setUsername("XYZ");
> dataSource.setUPassword("XYZ");
>
> ?dataSource=#myD
());
never faced any issue yet ?.
--
View this message in context:
http://camel.465427.n5.nabble.com/Dynamic-datasource-with-Camel-2-15-x-tp5772178p5772181.html
Sent from the Camel - Users mailing list archive at Nabble.com.
// Here I build my route
from("direct:xyz")
.to("jdbc:myDataSource")
}
}
Thank you for help
--
View this message in context:
http://camel.465427.n5.nabble.com/Dynamic-datasource-with-Camel-2-15-x-tp5772178.html
Sent from the Camel - Users mailing list archive at Nabble.com.
;
> // Here I build my route
> from("direct:xyz")
> .to("jdbc:myDataSource")
> }
> }
>
> Thank you for help
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Dynamic-datasource-with-Camel-2-15-x-tp5772178.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
Kind regards
Joakim Bjørnstad
s message in context:
http://camel.465427.n5.nabble.com/Dynamic-DataSource-tp5771402p5771487.html
Sent from the Camel - Users mailing list archive at Nabble.com.
You can build the uri dynamic as in this FAQ
http://camel.apache.org/how-to-use-a-dynamic-uri-in-to.html
On Thu, Sep 10, 2015 at 1:56 PM, arnaud <arnaud.merc...@free.fr> wrote:
> Hello,
>
> Id'like to use a dynamic datasource with the camel-sql component but it's
> not wo
vax.sql.DataSource
Arnaud
--
View this message in context:
http://camel.465427.n5.nabble.com/Dynamic-DataSource-tp5771402p5771427.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Is the dataSource configured in your context?
Best,
Christian
Am 10.09.2015 13:56 schrieb "arnaud" <arnaud.merc...@free.fr>:
> Hello,
>
> Id'like to use a dynamic datasource with the camel-sql component but it's
> not woking as I expected:
> After a search on
Hello,
Id'like to use a dynamic datasource with the camel-sql component but it's
not woking as I expected:
After a search on the forum, I have found a topic "Dynamic DataSource for
SQL", I try to do something similar :
from("direct:create")
.setHeader("dataSource",
Thanks for the advice. I've tried to implement this. Here's what my code looks
like:
from(direct:lookup)
.process(new Processor() {
public void process(Exchange exchange) throws Exception {
MemberRequest request =
exchange.getIn().getBody(MemberRequest.class);
Hi
Ah dataSource=:#dataSource should just be #dataSource, eg as its a
regular lookup in the registry. See more at
http://camel.apache.org/how-do-i-configure-endpoints.html
Its only the SQL component that has that special :#key for the SQL
placeholders (eg with a colon).
On Mon, Jun 9, 2014 at
I'm not sure that's it. It's almost like the SQL Component doesn't like column
names specified in the SQL. I tried changing it to SELECT * FROM MEMBER and
then hard-coding the dataSource name to match a bean name, and it works. I
guess I can live with using select *, but you'd think any valid
On Mon, Jun 9, 2014 at 8:50 PM, Matt Raible m...@raibledesigns.com wrote:
I'm not sure that's it. It's almost like the SQL Component doesn't like
column names specified in the SQL. I tried changing it to SELECT * FROM
MEMBER and then hard-coding the dataSource name to match a bean name, and
On Jun 9, 2014, at 1:03 PM, Claus Ibsen claus.ib...@gmail.com wrote:
On Mon, Jun 9, 2014 at 8:50 PM, Matt Raible m...@raibledesigns.com wrote:
I'm not sure that's it. It's almost like the SQL Component doesn't like
column names specified in the SQL. I tried changing it to SELECT * FROM
Den mandag den 9. juni 2014 skrev Matt Raible m...@raibledesigns.com:
On Jun 9, 2014, at 1:03 PM, Claus Ibsen claus.ib...@gmail.com
javascript:; wrote:
On Mon, Jun 9, 2014 at 8:50 PM, Matt Raible m...@raibledesigns.com
javascript:; wrote:
I'm not sure that's it. It's almost like the SQL
Hi
If you se to then the uri is computed statically, eg once when the
route is initialized.
So the dynamic to is a good practice for dynamic uris
http://camel.apache.org/how-to-use-a-dynamic-uri-in-to.html
As you can the pass in the dataSource parameter dynamically. As well
construct the SQL
Hello Matt,
You'll have to use the recipient list [1] pattern:
from(direct:projects)
.setProperty(ds, /* logic to convert client param to datasource name
*/)
.setHeader(target, simple(sql:select * from projects order by
id?dataSource=${property.ds})
.recipientList(header(target))
Hello,
I'm converting services written with IBM Message Broker 6.1 to Apache Camel.
Here's some of the logic I'm trying to convert:
SET Environment.Variables.dataSource = '';
CASE UPPER(InputRoot.XMLNSC.ns:memberLookupRequest.ns:args0.ax21:Client)
WHEN 'client1' THEN SET
20 matches
Mail list logo
