[
https://issues.apache.org/jira/browse/QPID-7773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16168886#comment-16168886
]
ASF subversion and git services commented on QPID-7773:
-------------------------------------------------------
Commit a0eaf5c157554489da55960f20dd3a4f7292f921 in qpid-broker-j's branch
refs/heads/master from [~k-wall]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=a0eaf5c ]
QPID-7773: [Java Broker] [Perf Tests] Really restore compatibility with older
Java Brokers.
> REST API queries that identify a single object by its full path should return
> a object rather than a list.
> ----------------------------------------------------------------------------------------------------------
>
> Key: QPID-7773
> URL: https://issues.apache.org/jira/browse/QPID-7773
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Reporter: Keith Wall
> Fix For: qpid-java-broker-7.0.0
>
>
> Currently if I GET for, say a queue, by the object's full path
> {{/queue/vhn/vh/myqueue}}, I get a JSON list contain the queue object, rather
> than an object directly. This makes the REST API's abstraction inconsistent:
> I PUT a queue as an object, but GET gives me a list.
> The REST API should be returning a list only in those situations where a
> multiple object response could arise e.g. {{/queue/vhn/vh}}, wildcards or
> filtering.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
