1 Reply Latest reply on Nov 7, 2007 12:27 PM by Kurt Stam

    Design of aggregator service

    Jaroslaw Kijanowski Newbie

      Currently the aggregator service creates a seperate message for every message it gets. I think the aggregator should wait for *all* messages, which belong together, and then, after all arrived, create one big message and send it to the next action item.

      This can be easily reproduced with the aggregator QS by delaying the red, blue or green service. You will notice that the print-after method is called several times instead of only one time (when all 3 messages finally arrived and were aggregated to one message).