Sep 16th, 2008, 08:53 AM
MessageID, correlationID ... don't we need a Strategy abstraction for Request/Reply ?
on this forum multiple threads expose requirement for Request/Reply pattern on JMS, with spring-jms template or Spring integration.
Even Spring-WS uses the hard-coded "Reply.correlationId = Request.messageId" option, according to SOAP over JMS spec...
Couldn't Spring define an abstraction for the Strategy used to link the Request with its response ? We could have two implementation :
- one for Reply.correlationId = Request.messageId
- one for Reply.correlationId = Request.correlationId (user define)
What's your opinion ?