[
http://jira.amdatu.org/jira/browse/AMDATUOPENSOCIAL-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivo Ladage - van Doorn resolved AMDATUOPENSOCIAL-89.
----------------------------------------------------
Assignee: Ivo Ladage - van Doorn
Resolution: Fixed
The problem was that the PersonServiceImpl assumed that there are always
OpenSocial properties available for a User. But initially, when a user is just
created in UserAdmin (like the default user 'Administrator'). the opensocial
properties are not yet available.
Updated the service to deal with that situation.
> newFetchPersonRequest from the JavaScript interface doesn't work properly
> --------------------------------------------------------------------------
>
> Key: AMDATUOPENSOCIAL-89
> URL: http://jira.amdatu.org/jira/browse/AMDATUOPENSOCIAL-89
> Project: Amdatu OpenSocial
> Issue Type: Bug
> Components: OpenSocial services
> Affects Versions: 0.2.0
> Reporter: Manuel Stampe
> Assignee: Ivo Ladage - van Doorn
> Fix For: 0.2.0
>
> Attachments: personServiceImplTest.xml
>
>
> A newFetchPersonRequest makes an RPC call to the function getPerson in
> PersonServiceImpl.java.
> The function however gets not the correct user id.
> Maybe because the person service is not tenant aware itself?
> The attached XML makes such a call when clicked on "Fetch people and friends"
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Amdatu-developers mailing list
[email protected]
http://lists.amdatu.org/mailman/listinfo/amdatu-developers
