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
On Tue, Jan 24, 2012 at 7:53 PM, pvenini wrote:
> Hi, I'm developing a info distribution system that gets an XML document with
> data entries and then has to enrich it with nodes that are obtained from a
> SQL database. The SQL query has to be generated using paramethers from data
> inside the ori
If you use the enrich EIP, you have to provide an Aggregation strategy to
"merge" the original exchange (which contains the xml document) and the new
exchange (the result of your database call if you have on). Where is the
problem?
Best,
Christian
On Tue, Jan 24, 2012 at 7:53 PM, pvenini wrote:
