[
https://issues.apache.org/jira/browse/AMQ-4072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Vincent reopened AMQ-4072:
----------------------------------
I believe the JMSCorrelationID is a message header field, not a message
property. While I see the following code excerpt from MessageServlet.java spins
through the message properties and adds HTTP response headers, I don't believe
that includes the JMSCorrelationID.
---------
protected void setResponseHeaders(HttpServletResponse response, Message
message) throws JMSException {
response.setHeader("destination", message.getJMSDestination().toString());
response.setHeader("id", message.getJMSMessageID());
// Return JMS properties as header values.
for(Enumeration names = message.getPropertyNames(); names.hasMoreElements() {
String name = (String) names.nextElement(); response.setHeader(name ,
message.getObjectProperty(name).toString()); }
}
---------
> RESTful HTTP interface responses do not contain a correlation ID header
> -----------------------------------------------------------------------
>
> Key: AMQ-4072
> URL: https://issues.apache.org/jira/browse/AMQ-4072
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.6.0
> Environment: RESTful HTTP client
> Reporter: Stephen Vincent
> Priority: Critical
> Fix For: 5.7.0
>
> Attachments: CorrelId.java
>
>
> When using a RESTful HTTP client to GET a message that has a correlation ID,
> the correlation ID is not sent as a header in the response from the broker.
> This inhibits my RESTful HTTP client from performing request-response.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
