Spring Data Rest - Bean validation is not applied to PUT method?

Question

I have a domain class defined as follows

@Data
@Entity
public class City {

    @Id
    @GeneratedValue(strategy = GenerationType.IDENTITY)
    @Column(name = "id")
    private long cityID;

    @NotBlank(message = "City name is a required field")
    private String cityName;


}

When I post to the endpoint http://localhost:8080/cities without a cityName I get a ConstraintViolationException but when I send a PUT request to the endpoint http://localhost:8080/cities/1 without a cityName I get the following exception instead of ConstraintViolationException.

{
  "timestamp": 1494510208982,
  "status": 500,
  "error": "Internal Server Error",
  "exception": "org.springframework.transaction.TransactionSystemException",
  "message": "Could not commit JPA transaction; nested exception is javax.persistence.RollbackException: Error while committing the transaction",
  "path": "/cities/1"
}

So how do I get a ConstraintViolationException exception for a PUT request?

Note: I am using Spring Data Rest so the endpoints are generated by Spring. There is no custom rest controller.

Possible duplicate of [PUT and POST fail on unknown properties Spring different behavior](http://stackoverflow.com/questions/34545997/put-and-post-fail-on-unknown-properties-spring-different-behavior) — pvpkiran, May 11 '17 at 13:51
I am using Spring Data Rest so Spring is generating endpoints at run-time so there is no need to implement a custom controller — Charlie, May 11 '17 at 13:56
@pvpkiran The linked question is about sending an unknown property but I am sending a null value for cityName so that question does not help — Charlie, May 11 '17 at 13:58
In my SDR project (spring-boot 1.4.3) validation works as expected. Field definition example: `@NotNull(message = "valid.field")` `@Pattern(regexp = NAME_PATTERN, message = "valid.username")` `@Column(nullable = false)` `private String name;` — Cepr0, May 12 '17 at 19:52
@Cepr0 Is there a way I can see the domain class, repository file and pom.xml? — Charlie, May 14 '17 at 08:22
@DeltaCharlie https://github.com/Cepr0/restvotes/tree/v1.1 (note - you need branch 'v1.1') — Cepr0, May 15 '17 at 06:35
@DeltaCharlie don't use v1.1 - it's obsolete. Use v.1.1.1: https://github.com/Cepr0/restvotes/tree/v.1.1.1 — Cepr0, May 15 '17 at 07:31
@DeltaCharlie 'v.1.1.1' - it's a branch in my project which you need. — Cepr0, May 15 '17 at 09:23

score 0 · Answer 1 · answered Jun 12 '17 at 12:34

I think Cepr0's test work for both PUT and POST, because when you send a PUT request for a non-existing entity then Spring Data Rest uses the create method in the background. Let's assume there is no user with id=100: calling 'PUT users/100' is the same as calling 'POST users/'

When you send PUT for an existing entity, it will generate that nasty TransactionSystemException.

I'm also fighting with the Data Rest exception-handling right now, and there are a lot of inconsistency in there.

Here is my current RestErrorAttributes class, it solves most of my problems, but there is a good chance I will fond others during the following days. :)

@Component
@Slf4j
public class RestErrorAttributes extends DefaultErrorAttributes implements MessageSourceAware {

private MessageSource messageSource;

@Override
public void setMessageSource(MessageSource messageSource) {
    this.messageSource = messageSource;
}

/** {@inheritDoc} */
@Override
public Map<String, Object> getErrorAttributes(RequestAttributes requestAttributes, boolean includeStackTrace) {

    final Map<String, Object> errorAttributes = super.getErrorAttributes(requestAttributes, includeStackTrace);
    // Translate default message by Locale
    String message = errorAttributes.get("message").toString();
    errorAttributes.put("message",
            messageSource.getMessage(message, null, message, LocaleContextHolder.getLocale()));
    // Extend default error message by field-errors
    addConstraintViolationDetails(errorAttributes, requestAttributes);
    return errorAttributes;
}

private void addConstraintViolationDetails(Map<String, Object> errorAttributes,
        RequestAttributes requestAttributes) {
    Throwable error = getError(requestAttributes);
    if (error instanceof ConstraintViolationException) {
        errorAttributes.put("errors",
                RestFieldError.getErrors(((ConstraintViolationException) error).getConstraintViolations()));
    }
    else if (error instanceof RepositoryConstraintViolationException) {
        errorAttributes.put("errors", RestFieldError
                .getErrors(((RepositoryConstraintViolationException) error).getErrors().getAllErrors()));
    }
}

/** {@inheritDoc} */
@Override
public ModelAndView resolveException(HttpServletRequest request, HttpServletResponse response, Object handler,
        Exception ex) {

    try {
        Throwable cause = ex;
        while (cause instanceof Exception) {
            // Handle AccessDeniedException - It cannot be handled by
            // ExceptionHandler
            if (cause instanceof AccessDeniedException) {
                response.sendError(HttpStatus.FORBIDDEN.value(), cause.getMessage());
                super.resolveException(request, response, handler, (Exception) cause);
                return new ModelAndView();
            }
            // Handle exceptions from javax validations
            if (cause instanceof ConstraintViolationException) {
                response.sendError(HttpStatus.UNPROCESSABLE_ENTITY.value(), "validation.error");
                super.resolveException(request, response, handler, (Exception) cause);
                return new ModelAndView();
            }
            // Handle exceptions from REST validator classes
            if (cause instanceof RepositoryConstraintViolationException) {
                response.sendError(HttpStatus.UNPROCESSABLE_ENTITY.value(), "validation.error");
                super.resolveException(request, response, handler, (Exception) cause);
                return new ModelAndView();
            }
            cause = ((Exception) cause).getCause();
        }
    } catch (final Exception handlerException) {
        log.warn("Handling of [" + ex.getClass().getName() + "] resulted in Exception", handlerException);
    }
    return super.resolveException(request, response, handler, ex);
}

@Getter
@AllArgsConstructor
public static class RestFieldError {
    private String field;
    private String code;
    private String message;

    public static List<RestFieldError> getErrors(Set<ConstraintViolation<?>> constraintViolations) {
        return constraintViolations.stream().map(RestFieldError::of).collect(Collectors.toList());
    }

    public static List<RestFieldError> getErrors(List<ObjectError> errors) {
        return errors.stream().map(RestFieldError::of).collect(Collectors.toList());
    }

    private static RestFieldError of(ConstraintViolation<?> constraintViolation) {
        return new RestFieldError(constraintViolation.getPropertyPath().toString(),
                constraintViolation.getMessageTemplate(), constraintViolation.getMessage());

    }

    private static RestFieldError of(ObjectError error) {

        return new RestFieldError(error instanceof FieldError ? ((FieldError) error).getField() : null,
                error.getCode(), error.getDefaultMessage());

    }
}

}

score 0 · Answer 2 · answered Apr 17 '19 at 16:13

My workaround for this was to setup an exception handler to handle the TransactionSystemException, unwrap the exception and handle like a regular ConstraintViolationException:

@ExceptionHandler(value = {TransactionSystemException.class})
public ResponseEntity handleTxException(TransactionSystemException ex) {
    Throwable t = ex.getCause();
    if (t.getCause() instanceof ConstraintViolationException) {
        return handleConstraintViolation((ConstraintViolationException) t.getCause(), null);
    } else {
        return new ResponseEntity(HttpStatus.INTERNAL_SERVER_ERROR);
    }
}

@ExceptionHandler({ConstraintViolationException.class})
public ResponseEntity<Object> handleConstraintViolation(ConstraintViolationException ex,
          WebRequest request) {
    List<String> errors = new ArrayList<>();
    for (ConstraintViolation<?> violation : ex.getConstraintViolations()) {
        errors.add(violation.getRootBeanClass().getName() + " " + violation.getPropertyPath() + ": " + violation.getMessage());
    }

    return new ResponseEntity<>(errors, new HttpHeaders(), HttpStatus.CONFLICT);
}

Spring Data Rest - Bean validation is not applied to PUT method?

2 Answers2