[ https://issues.apache.org/activemq/browse/SM-744?page=comments#action_37422 ] Grant McDonald commented on SM-744: -----------------------------------
That clarifies things quite a bit. I can see that in certain circumstances that this would be useful. The only thing to keep in mind is that such configuration is static for the lifetime of the endpoint - but I guess your client isn't going to be expecting it to be any different. I would like to hear what Guillaume has to say about such configuration options and whether it's appropriate or not. Can you please attach a patch of your changes? > Request/Response for jms through MessageID/CorrelationID > -------------------------------------------------------- > > Key: SM-744 > URL: https://issues.apache.org/activemq/browse/SM-744 > Project: ServiceMix > Issue Type: Improvement > Components: servicemix-jms > Environment: All platforms > Reporter: Martin Landua > Priority: Minor > > The servicemix-jms component assumes that the request/reponse pattern is > implemented by the client by using some artificial correlation id as the > "connection" between the messages (as described in > http://activemq.org/site/how-should-i-implement-request-response-with-jms.html). > However, there are cases where the client assumes that the server sets the > correlation id of the response to the message id (!) of the request. > Currently, the servicemix-jms component does not support this, but it would > be convenient if it were configurable. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
