That sounds good. I think we need an over arching tr catch block to ensure that whatever else we do right or wrong we somehow at least return xml,json or what have you. On 3 Oct 2014 14:32, "Morten Olav Hansen" <morte...@gmail.com> wrote:
> > On Thu, Oct 2, 2014 at 8:51 PM, Bob Jolliffe <bobjolli...@gmail.com> > wrote: > >> https://blueprints.launchpad.net/dhis2/+spec/web-api-error-messages >> > > I saw your comment Bob, and yes, we will be watching the accept header > (this was mentioned in call just before you joined ;-)). I'm not sure how > much I will be able to get in for 2.17, but at least I should be able to > define the model, and provide more robust feedback in > AbstractCrudController, and then we can extend on that for 2.18. > > I'm also planing to keep all web-api messages in i18n files, so that we > can also translate on output (if available). We should also introduce coded > error/info messages, so that its easier for the third party client to know > what is happening, returning conflict and a message is not really enough. > > -- > Morten >
-- Mailing list: https://launchpad.net/~dhis2-devs-core Post to : dhis2-devs-core@lists.launchpad.net Unsubscribe : https://launchpad.net/~dhis2-devs-core More help : https://help.launchpad.net/ListHelp
