Custom exceptions instead of exception handling

[h1alexbel]

now we doing something like this:

throw new ResourceAlreadyExistsException(...);

and we do support exception handling via Spring Exception Handlers:

pmo/src/main/java/git/tracehub/pmo/controller/AdviceController.java

Lines 76 to 87 in 385414f

	@ExceptionHandler(ResponseStatusException.class)
	public ResponseEntity<byte[]> handle(
	final ResponseStatusException exception
	) {
	return new Logged(
	exception,
	new RestError(
	exception.getMessage(),
	HttpStatus.valueOf(exception.getStatusCode().value())
	)
	).value();
	}

We actually can get rid of this by making all our custom exceptions extend HttpStatusException. After this all of them will be handled by Spring

@hizmailovich wdyt?

[dukris]

But for now our custom exceptions are already inherited from ResponseStatusException. Why would it be better to replace it with HttpStatusException? We will still need to handle it in ControllerAdvice...

[h1alexbel]

@hizmailovich If we do inherit HttpStatusException then we can remove Exception Handling inside ControllerAdvice