Application deployed successfully: [application]
>>> subscription-c1', u'statusCode': 202}
>>>
>>>
>>>
>>> Current (new) return msg:
>>>
>>> {u'message': u'Application deployed successfully: [application]
>>> s
cation deployed successfully: [application]
>> subscription-c1', u'statusCode': 202}
>>
>>
>>
>> Thanks
>>
>>
>>
>> Martin
>>
>>
>>
>> *From:* Imesh Gunaratne [mailto:im...@apache.org]
>> *Sent:* Sa
>
> 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 pre
15 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&quo
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 wrote:
> the order of the fields does not IMO. For in
the order of the fields does not IMO. For instance a client/UI may extract
the message and display.
Hi Mary,
I have a couple of questions here regarding the significance of this field
in the response body.
1. I remember a discussion where it was considered to remove the
"statusCode" since it is duplicate information. I'm not sure what was the
conclusion in that discussion. However, having the s
