[
https://issues.apache.org/jira/browse/QPID-6948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15147280#comment-15147280
]
Rob Godfrey commented on QPID-6948:
-----------------------------------
Also, currently we have under /service :
# /service/userpreferences
# /service/preferences
# /service/structure
# /service/queuereport
# /service/metadata
Of these I think 1,2,3 and 5 should all actually be versioned and thus under
/api. For Queue Reports since the idea of these is to allow those running a
Qpid instance to inject their own reporting code into the broker, I don't think
it makes sense to version these with the model version.
For backward compatibility I guess the service/foo mapping must be maintained
and should always return the "6.0" version of these servlets
> Introduce REST API compatibility layer
> --------------------------------------
>
> Key: QPID-6948
> URL: https://issues.apache.org/jira/browse/QPID-6948
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Reporter: Keith Wall
>
> Make the REST API backwardly compatibility with model as used by 0.32.
> In general the compatibility layer should:
> For GET:
> * attributes that are removed should be simulated (e.g. defaultVirtualHost)
> * new attributes/new types don't need to be hidden
> For POST/PUT:
> * on creation, new mandatory attributes should be given sensible defaults
> * removed operations should be supported perhaps by rewriting the request in
> terms of new operations.
> When the model changes structurally, the compatibility layer should present
> the old model.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
