[
https://issues.apache.org/jira/browse/QPID-6626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14617481#comment-14617481
]
Keith Wall commented on QPID-6626:
----------------------------------
Two comments:
# There is a discrepancy between the way the VersionsServlet reports supported
versions (as bare numbers e.g. "3") and what we expect embedded in the API URL
(where the number must be prefixed with a letter 'v' e.g. /api/v3). Is there
good reason for this? It will make automatic discovery slightly harder.
# Not specifically a comment on this commit but currently a request for an
unsupported version (e.g. http://localhost:8080/api/v4/broker/) returns a 200
OK and a non-JSON response. I think a 404 would be more appropriate and make
programmatically managing groups which may not be at the same version more
straightforward.
> [Java Broker] Provide a mechanism for the REST API to communicate which
> versions are supported
> ----------------------------------------------------------------------------------------------
>
> Key: QPID-6626
> URL: https://issues.apache.org/jira/browse/QPID-6626
> Project: Qpid
> Issue Type: Improvement
> Reporter: Rob Godfrey
> Assignee: Rob Godfrey
> Fix For: 6.0 [Java]
>
>
> The REST API has a notion of version, and it is planned that future releases
> will provide some limited capability to support prior versions of the API,
> however there is currently no easy way to determine the versions of the API
> supported by a given broker
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
