I'm currently getting our service layer to comply with the filtering
options described:
http://opensocial-resources.googlecode.com/svn/spec/draft/REST-API.xml#standardQueryParameters
This is particularly because I need to be able to support calls like:
/people/@me/@self?filter...@friends&filterOp=contains&filterValue=<someUserId>
The problem is that PersonService defines a getPerson method that does
not use CollectionOptions and PersonHandler will always call getPerson
for that URL:
if (userIds.size() == 1) {
if (optionalPersonId.isEmpty()) {
if (groupId.getType() == GroupId.Type.self) {
return personService.getPerson(userIds.iterator().next(),
fields, request.getToken());
Does anyone have a strategy for dealing with this? Would it be such a
bad thing if PersonService only exposed getPeople()?
Cheers,
Ben Smith
BBC
