Asynchronous request reply correlation (again)

[Gary Russell]

Deleted: See May21 11:23pm post for a better work-around.

[Diego Bravo]

Yep, anyway tried the first suggestion with the same exception. Yet I didn't try extending the AbstractAggregatingMessageGroupProcessor.

For the other suggestion, I believe that the header-enricher will need access to the aggregator's MessageStore in order to do the correlation by itself and find the request message. My correlation/release beans are stateless so I can't see how they will help me, or I'm missing something?

Thanks for your help!

[Gary Russell]

Here's a cleaner work-around; I just tested this and it works fine...

public Message<String> aggregate(List<Message<String>> in) {
	return MessageBuilder.fromMessage(in.get(1))
		.setHeader("requestReplyChannel", in.get(0).getHeaders().getReplyChannel())
		.build();
}

<int:aggregator input-channel="in" ref="agg" output-channel="route.reply"/>

<int:header-enricher input-channel="route.reply">
	<int:header name="replyChannel" expression="headers.requestReplyChannel"/>
</int:header-enricher>
	
<bean id="agg" class="org.myco.aggregator.gpr.GprAgg"/>

i.e. Copy the replyChannel to a temporary header; route the aggregator output to a header-enricher, and voila.

[Diego Bravo]

it's working for me too... Awesome!

Thanks a lot for your help and patience Gary!

[Gary Russell]

Glad to help.

I opened an improvement JIRA issue https://jira.springsource.org/browse/INT-1913, if you want to watch it.

[Gary Russell]

BTW, this works too..

public Message<String> aggregate(List<Message<String>> in) {
	return MessageBuilder.fromMessage(in.get(1))
		.setReplyChannel((MessageChannel) in.get(0).getHeaders().getReplyChannel())
		.build();
}

<int:aggregator input-channel="in" ref="agg" output-channel="route.reply"/>

<int:service-activator input-channel="route.reply" expression="payload"/>

But it's perhaps not as obvious as to why it works :-)