[
https://issues.apache.org/jira/browse/AMQ-3857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-3857.
-------------------------------
Resolution: Fixed
Fix Version/s: 5.7.0
Assignee: Timothy Bish
Using the response headers seems sensible. Applied the patch and supplied test
case, thanks!
> MessageServlet get messages does not return JMS Message Properties
> ------------------------------------------------------------------
>
> Key: AMQ-3857
> URL: https://issues.apache.org/jira/browse/AMQ-3857
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.5.0, 5.6.0
> Reporter: Alan Hudson
> Assignee: Timothy Bish
> Fix For: 5.7.0
>
> Attachments: amq-3857.patch, amq-3857.patch
>
> Original Estimate: 6h
> Remaining Estimate: 6h
>
> When using GET to get a message it does not return any of the JMS message
> properties.
> I can easily see how to add that code, but I'm not sure what the correct way
> to return them is. They could go into the response headers via
> setResponseHeaders or the returned XML format could be changed to support
> properties and the header. Sadly this would likely break most existing
> clients.
> We'd like to use the REST API to enable some web clients to fully participate
> in a messaging system that is primarily Java based.
> If we can come to agreement on how we want to return properties then I'd be
> happy to code up a patch.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
