qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lorenz Quack (JIRA)" <j...@apache.org>
Subject [jira] [Reopened] (QPID-7773) REST API queries that identify a single object by its full path should return a object rather than a list.
Date Thu, 21 Sep 2017 08:58:00 GMT

     [ https://issues.apache.org/jira/browse/QPID-7773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Lorenz Quack reopened QPID-7773:
--------------------------------

> 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: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org


Mime
View raw message