Hi All our endpoint have now been switched our to using the new field filtering (similar to the old inclusion/exclusion), so the data you want is probably there, but you have to tell the system you want to have it. I do see that there is a bug in the UserCredentials class, I will fix that tomorrow.
Please see the documentation here: http://www.dhis2.org/doc/snapshot/en/user/html/ch30s07.html Regarding the the custom serializers, we needed a bit more custom control over the output, we still use Jackson (ObjectMapper, but not data-binding) in the backend, together with xml (StAX). -- Morten On Tue, Jun 10, 2014 at 1:02 PM, Mahendra Kariya <mahen...@thoughtworks.com> wrote: > Hello Morten, > > We're facing some issues due to some recent changes to UserController. > > The serialized 'User' json has some issues. > > The 'usercredentials' field is now being serialized as > 'org.hisp.dhis.user.UserCredentials' and also some of the properties of > UserCredentials (like userAuthorityGroup ) is not being serialized. > > One of our application is breaking due to these contract changes. We tried > fixing it, but soon got lost in the custom serialization code. > > Can you please have a look at this. > > ( Also on a side note, is there any specific reason we are going for > custom serialization instead of going for standard serializers like > Jackson? ) > > > Regards > > Mahendra/Kiran > > >
_______________________________________________ Mailing list: https://launchpad.net/~dhis2-devs Post to : dhis2-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~dhis2-devs More help : https://help.launchpad.net/ListHelp
