[
https://issues.apache.org/jira/browse/SHINDIG-904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ben Smith resolved SHINDIG-904.
-------------------------------
Resolution: Invalid
Discussion on mailing list determined that having PersonHandler only use
getPeople() would be a better solution.
> Update PersonService to help support 0.9 Spec filter options
> ------------------------------------------------------------
>
> Key: SHINDIG-904
> URL: https://issues.apache.org/jira/browse/SHINDIG-904
> Project: Shindig
> Issue Type: Improvement
> Components: Java
> Affects Versions: trunk
> Reporter: Ben Smith
> Fix For: trunk
>
> Attachments: SHINDIG-904-improvement-741538.patch
>
>
> Filter options are defined in 0.9 to help provide information like 'are these
> two users friends':
> http://opensocial-resources.googlecode.com/svn/spec/draft/REST-API.xml#standardQueryParameters
> These are currently wrapped in CollectionOptions and it is down to the
> implementation of PersonService to provide the requested filtering.
> The problem is, PersonService.getPerson() method signature does not include
> CollectionOptions which precludes the all important
> /people/@me/@self?filter...@friends&filterOp=contains&filterValue=<someUserId>
> This can be solved by adding CollectionOptions to the method signature. While
> this will alter the interface, which isn't something that you should do
> lightly, this is necessary if you want to adhere to the response format for
> /people/@me/@self requests (a single marshaled person rather than a restful
> collection).
> Patch to come.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
