[jira] Updated: (SHINDIG-318) DataAdapter entries not implemented

["David Primmer (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SHINDIG-318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Primmer updated SHINDIG-318:
----------------------------------

    Attachment: shindig-318_update_dataAdapter.patch

This patch adds an getEntry to the DataAdapter and makes APPDATA_OF_APP_OF_USER an entry, not a collection. 

It also makes some minor changes to the code to make it look like the other adapters (not using the "entry" variable name that is from the parent so that there's a clearer distinction of when we're working with FOM objects versus Social POJOs.)

Adds a large atom test for both routes in the adapter.

> DataAdapter entries not implemented
> -----------------------------------
>
>                 Key: SHINDIG-318
>                 URL: https://issues.apache.org/jira/browse/SHINDIG-318
>             Project: Shindig
>          Issue Type: Bug
>          Components: RESTful API (Java)
>            Reporter: David Primmer
>         Attachments: shindig-318_update_dataAdapter.patch
>
>
> APPDATA_OF_APP_OF_USER "/appdata/{uid}/@self/{aid}" needs to be implemented as an TargetType.TYPE_ENTRY and it should return a single Entry and not a list/collection/feed. Currently it's processed as a collection and sent to getEntries with APPDATA_OF_FRIENDS_OF_USER, so it's generated as a feed document. 
> There are a few nitpicky issues with it as well. Shouldn't the data interface support just getting a single person's appdata and not return a list similar to the people and activity services?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.