[
https://issues.apache.org/jira/browse/QPID-7247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15370927#comment-15370927
]
Keith Wall commented on QPID-7247:
----------------------------------
Please see commit 1752170
# Wildcard responses are always a list. Each list entry will contain the
preferences belonging to exactly one configured object, so all preferences will
share the same {{assoicatedObjec}} id. I don't think you could say they are
lumped together.
# re. {{Sets.newHashSet()}} - is slightly cleaner if you want a set of greater
than one member. It turns out I didn't need it, so I have gone back to
{{Collections.singleton()}}
# formatting - done
# {{#isWild()}} - renamed as suggested.
# Re. filtering - I think this was required otherwise an {{id=}} would have
been interpreted as both a ConfiguredObject ID and an Preference ID. I wanted
to reuse RestServlet#getTargetObjects but need to do so without accepting the
filters.
> Implement preferences model and REST API
> ----------------------------------------
>
> Key: QPID-7247
> URL: https://issues.apache.org/jira/browse/QPID-7247
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Reporter: Keith Wall
> Assignee: Keith Wall
> Fix For: qpid-java-6.1
>
>
> Implement the preferences model and the REST API described by:
> https://cwiki.apache.org/confluence/display/qpid/Preference+Store
> After this work it will be possible to add/update/remove preference from the
> REST API, but there will be no persistence. At this stage all preferences
> will be available to all users. There will be no security in preferences
> layer.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
