[
https://issues.apache.org/jira/browse/AMQ-4072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13464216#comment-13464216
]
Stephen Vincent commented on AMQ-4072:
--------------------------------------
I realize that the open source community relies on contributors and I should
contribute more than this jira. My management sets my priorities, and like
most, I have more on my plate than I have time for. I do appreciate the help I
received, and I hope I can contribute some time in the future. I sincerely do
wish to.
The goal of this comment is provide more information regarding my use case.
The main purpose of this jira, is to report that a message's JMSCorrelationID
header field, does not flow back along with the response headers. The attached
java test illustrates that issue. I realize that beginning with 5.7, message
"properties" will flow back as headers in the response. However, the
JMSCorrelationID does not because it is not property. My use case hinges on
the customers that expect my application to be able to obtain the correlation
ID. Given that I have chosen to implement my application using the HTTP
interface, my application is currently unable to obtain the JMSCorrelationID.
Aside from getting the JMSCorrelationID in the response to a GET request,
another use case involves POSTing a message that contains a correlation ID.
Using an url-encoded content-type, or specifying the JMSCorrelationID in a
query parameter are two says to post a message with a JMSCorrelationID.
However, both of those mechanisms have limitations.
In one use case, see a customer using a client that is able to set the
JMSCorrelationID when putting a message on the queue, and then expecting my
client application to obtain it when getting the message off of the queue. I
also see a use case where I want to post many messages containing different
correlation IDs, all from a single connection to the broker.
> 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: Transport
> Affects Versions: 5.6.0
> Environment: RESTful HTTP client
> Reporter: Stephen Vincent
> Fix For: 5.8.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
