[
https://issues.apache.org/jira/browse/AMQ-4072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13464134#comment-13464134
]
Stephen Vincent commented on AMQ-4072:
--------------------------------------
Thanks for the suggestion. I do sincerely appreciate the help. I just took a
quick look at fusemq-c. At a glance, I see UNIX, Windows and Mac; but not
z/OS. We still have many customers running applications on 31-bit MVS
mainframes. Being able to support those customers played a part in my decision
to go with HTTP. I assume the fusemq-c client may have some code that assumes
an ASCII character set, and probably depends on the C run-time library. Even
if fusemq-c has not dependencies on ASCII, if it has many C runtime
dependencies, it would take a significant amount of work to over-come if I
wanted to use it on MVS.
> 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
