Okay so you are using grouped exchange option. Then its a bit different. The data is stored as a property on the exchange as a list.
Okay so you are using grouped exchange option. Then its a bit different. The data is stored as a property on the exchange as a list.
Instead of the processor you can use a POJO and bind a parameter to the property. But the List still contains Exchange objects so you need to invoke the getIn().getBody() methods on it. But if you do it like this you don't need to import any Camel API in the POJO.
Public Document mergeMyStuff(@Property("CamelGroupedExchange") List grouped) { Document parent = ... for (int I = 0; I GetBody(Documemt. Class); .. add to parent doc } return parent; }.
Thanks for your suggestion. This solution really looks better – archer Apr 29 '11 at 9:31.
If that's the case, then no. Currently that's required. We have on the roadmap to offer a pojo model for the aggregation so you don't need to use that Camel API.
So expect this to be simpler in the future.
No my custom aggregator is a simple processor receiving grouped exchanges. Edited my post putting the code sample there. – archer Apr 28 '11 at 18:00.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.