Hi Martin,
Yes this change will remain, however we will be removing statusCode
attribute and adding a new attribute called status. This will contain
either "successful" or "error".
Thanks
On Mon, May 11, 2015 at 4:39 AM, Martin Eppel (meppel) <mep...@cisco.com>
wrote:
> Question along the same lines, in a recent change the attribute
> “successMessage” got replace by “message” - this will remain or are there
> any plans to change it too ?
>
>
>
> e.g. previous (old) return msg:
>
> {u'successMessage': u'Application deployed successfully: [application]
> subscription-c1', u'statusCode': 202}
>
>
>
> Current (new) return msg:
>
> {u'message': u'Application deployed successfully: [application]
> subscription-c1', u'statusCode': 202}
>
>
>
> Thanks
>
>
>
> Martin
>
>
>
> *From:* Imesh Gunaratne [mailto:im...@apache.org]
> *Sent:* Saturday, May 09, 2015 9:27 AM
> *To:* dev
> *Subject:* Re: Sequential order of the REST API response message and
> status code is incorrect
>
>
>
> Yes the conclusion of the previous discussion was to remove statusCode
> attribute and add a new attribute called status. The status attribute could
> contain either "successful" or "error".
>
>
>
> Thanks
>
>
>
> On Sat, May 9, 2015 at 6:11 PM, Udara Liyanage <ud...@wso2.com> wrote:
>
> the order of the fields does not IMO. For instance a client/UI may
> extract the message and display.
>
>
>
>
>
> --
>
> Imesh Gunaratne
>
>
>
> Senior Technical Lead, WSO2
>
> Committer & PMC Member, Apache Stratos
>
--
Imesh Gunaratne
Senior Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
