Pablo,
my suggestion looks like the one below:
from("direct:start")
.enrich("direct:enrich", myAggregationStrategie)
.to("bean://doWhatEverYouWantWithTheEnrichedXML");
from("direct:enrich")
.to("bean://transformMyXmlIntoAQuery")
.to("jdbc://xxx");
Give it a try...
Best,
Christian
On W
Hi
The aggregator will take in the original exchange and then also the
exchange returned by the resource.
Give it a try.
Taariq
On Wed, Jan 25, 2012 at 4:19 PM, Pablo Venini wrote:
> Christian:
> as I see it, the problem would occur before the aggregation
> strategy; if I use a JDBC
Christian:
as I see it, the problem would occur before the
aggregation strategy; if I use a JDBC endpoint, the query would have to
be placed into the body of the exchange, thus replacing the original
body (the XML document, which I have to use later to merge with the
nodes I crea
>
> Pablo
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Enrich-message-with-data-from-dynamic-sql-query-tp5329427p5329427.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-
FuseSource
Email
this message in context:
> http://camel.465427.n5.nabble.com/Enrich-message-with-data-from-dynamic-sql-query-tp5329427p5329427.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
f the nodes).
I was thinking about using the enrich statement but I don't realize how can
I generate the dynamic query (using sql: or jdbc:) without loosing the
original XML document.
Thanks
Pablo
--
View this message in context:
http://camel.465427.n5.nabble.com/Enrich-message-with-data-fr
