(vlim); Martin Eppel (meppel); Imesh Gunaratne
Subject: Re: Re-factoring REST API
Hi,
This modification will expose the error status as 400 bad request, 404 not
found or 500 internal server error other than sending 400 bad request for every
server-side error.
Thanks.
On Thu, Apr 23, 2015 at 2:24
>
>
> *From:* Dinithi De Silva [mailto:dinit...@wso2.com]
> *Sent:* 23 April 2015 09:48
> *To:* dev
> *Cc:* Vanson Lim (vlim); Shaheedur Haque (shahhaqu); Martin Eppel
> (meppel); Imesh Gunaratne
> *Subject:* Re: Re-factoring REST API
>
>
>
> Hi,
>
>
>
>
[mailto:dinit...@wso2.com]
Sent: 23 April 2015 09:48
To: dev
Cc: Vanson Lim (vlim); Shaheedur Haque (shahhaqu); Martin Eppel (meppel); Imesh
Gunaratne
Subject: Re: Re-factoring REST API
Hi,
I have listed the changes in a point form below.
* In all the API methods the response message format
Hi,
I have listed the changes in a point form below.
- *In all the API methods the response message format will be changed to
display a status message either with "Success" or "Error" . Status code
will be removed from the response message.*
Eg:
*Current format*
return Response.status
Just to clarify we are only changing the HTTP status codes and response
message formats (of error and successful messages) in the REST API. We are
not changing any of the API method definitions or JSON definitions.
Dinithi: It would be great if you could list of out the changes in point
form.
Tha
Hi,
Please find the list of current status codes that are being used [1].
[1]
https://docs.google.com/spreadsheets/d/1orFbcvkrowtz_LKJL7IXzQgBBxloMkFICobZGxlKMuA/edit?usp=sharing
On Wed, Apr 22, 2015 at 11:15 AM, Dinithi De Silva
wrote:
> Hi all,
>
> We are in the process of re-factoring the R
Hi all,
We are in the process of re-factoring the REST API with the following
changes (As discussed in a separate mail thread - [Discuss] REST API
Improvements ).
1. *Moving non-API methods to StratosApiV41Utils class from **StratosApiV41
class*. (Refer the mail thread - API methods for tenants)
