This appears to be a bug in the codebase, sorry about that.
I'll log a JIRA and have it fixed straight away.
Great - thanks!
I'm wondering, is it possible to use StaticRouter/Aggregator and put names on the aggregatorTags? Now they are all unnamed, and it would be easier for meg if I could name them according to the service I use, so that when I merge them I can look for "serviceA" and "serviceB" as aggregatorTags. Is this possible?
I'll try to elaborate on my last question a little bit. I using a StaticRouter to send a request to two different services, and I then use the Aggregator and a transformer following it to merge the replies from these two services.
Both of the services have their own transformers attached, so that the replies are already transformed into a common domain-model when I try to merge them.
I would be much easier for me if I could know which service the different objects I try to merge come from, for example if something is wrong with the replies I can give more meaningful errormessages. But as long as the aggregatorTags are unnamed I haven't found a way to figure this out.
If there is any other way of doing this, like adding metadata to the messages or something like that, then that would work too. I'm thankful for any suggestions! :-)