The appId is part of the URI for app data requests
/{userId}+/{groupId}/{appId}
The appId specified is passed to AppDataService calls.
For most usages the appId will always be '@app' which substitutes the appId
from the security token
This in turn is almost always the gadgetUrl.
I haven't tested osapi.appdata for a while. Can you insure that you have
"appId":"@app" in your request?
On Wed, Aug 25, 2010 at 4:47 AM, Okke Harsta <[email protected]> wrote:
> We are implementing the persistent store of shindig Java and I have a
> question regarding the AppDataService. I was under the impression that
> AppData was tied to an user and a gadget/application, but from the
> return value of the AppDataService getPersonData it would appear that
> AppData is only tied the Person (and not to a specific gadget) as
> there is no way to specify the appId and personId in the
> DataCollection object (it is a Map<String, Map<String, String>> entry
> where the key of the Map is personId and the key a map of key/values).
> Am I missing something?
>
> Another question is regarding the appId: it is retrieved from the
> SocialRequestItem when delegating calls from the AppDataHandler to the
> AppService, but the appId is null in the examples I have tried. Does
> this require additional coding in the container.js to include the
> appId in the JavaScript call (we use the osapi.appdata)
>
> thanks,
> Okke
>
--
Paul Lindner -- [email protected] -- linkedin.com/in/plindner
