RE: JdbcAggregationRepository is not permanently?

2022-04-08 Thread Reto Peter
erchangeID. It took me a lot of time to find this solutionbut now it all works -Original Message- From: Karen Lease Sent: Friday, April 8, 2022 9:34 PM To: users@camel.apache.org Subject: Re: JdbcAggregationRepository is not permanently? Hi, To store the aggregated results, you need

Re: JdbcAggregationRepository is not permanently?

2022-04-08 Thread Karen Lease
Hi, To store the aggregated results, you need to create a separate table in your database. Then you can add something like the following statement to your route after the aggregation: .to("sql:insert into messages (doctype, messageID) values (:#doctype, :#messageID)"); The values of the

Re: JdbcAggregationRepository is not permanently?

2022-04-05 Thread Claus Ibsen
Hi If you mean that the tables are "cleaned up" then yes that is by design. The tables are storing in-progress aggregations, when they are completed and processed finished then their rows are deleted. On Tue, Apr 5, 2022 at 10:13 AM Reto Peter wrote: > > Hi > > Using the

JdbcAggregationRepository is not permanently?

2022-04-05 Thread Reto Peter
Hi Using the JdbcAggregationRepository I am trying to save the relation between my incoming messages and the aggregate, as a 1-n relation. It is actually the EDI Messages (Single message) into the EDI Interchange (Collection of messages). When I run the route, I see that the entries are