Trace:
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
jvx:communication:rest_exceptionhandling [2019/07/09 09:19] admin |
jvx:communication:rest_exceptionhandling [2019/07/09 09:24] admin |
||
|---|---|---|---|
| Line 2: | Line 2: | ||
| ~~Title: REST Exception handling~~ | ~~Title: REST Exception handling~~ | ||
| - | Our standard [[jvx:common:util:rest|REST services]] come with standard exception handling. This means that all server-side exceptions send the http status code 400 (Bad Request) to the client. The implementation already checks some exception types and returns custom http status codes: | + | Our standard [[jvx:common:util:rest|REST services]] come with standard exception handling. This means that all server-side exceptions will send the http status code 400 (Bad Request) to the client. The implementation already checks some exception types and returns custom http status codes: |
| ^ Exception ^ http status ^ | ^ Exception ^ http status ^ | ||
| - | | UnknownObjectException | 404 (not found) | | + | | UnknownObjectException | 404 (Not found) | |
| - | | SecurityException | 403 (forbidden) | | + | | SecurityException | 403 (Forbidden) | |
| - | | InvalidPasswordException | 401 (unauthorized) | | + | | InvalidPasswordException | 401 (Unauthorized) | |
| If you want custom status codes, it's possible to throw **RestServiceException**. This Exception class supports custom status codes and error messages. | If you want custom status codes, it's possible to throw **RestServiceException**. This Exception class supports custom status codes and error messages. | ||
| + | <file java> | ||
| + | if (!isBookingAvailable()) | ||
| + | { | ||
| + | throw new RestServiceException(501, "The booking feature isn't yet implemented!"); | ||
| + | } | ||
| + | |||
| + | ... | ||
| + | </file> | ||