bean-validation

I can't seem to be able to find a summary that distinguishes the difference between these three annotations. @NotNull : The CharSequence, Collection, Map or Array object is not null , but can be empty. @NotEmpty : The CharSequence, Collection, Map or Array object is not null and size > 0 . @NotBlank : The string is not null and the trimmed length is greater than zero . To help you understand, let's look into how these constraints are defined and carried out (I'm using version 4.1): The @NotNull constraint is defined as: @Constraint(validatedBy = {NotNullValidator.class}) This class has an

I have a very simple Spring Boot application that uses Spring-Data-Mongodb All I want to do is set a JSR-303 validation rule that says the object I'm saving must have a username. I read that JSR-303 was added to spring-data-mongodb in version 1.1 so I assumed that when I save an object it's validated but this isn't the case. Does anyone have a simple example setup that shows how this works? My User pojo looks like public class User { @Id private String id; @NotNull(message = "User Name is compulsory") private String userName; private String password; public User() {} public String getId() {

I see a lot of examples marking beans as entity beans (@Entity) & named beans (CDI), so as to avoid creating 2 classes (managed bean & entity bean) and also to make use of Bean Validation so that validation can be performed on both client & server. So should I be using a single class or not, are there any issues or should I be having my managed beans or service layer create entity beans using the data from managed beans ? Arjan Tijms The @Named or @ManagedBean annotations are typically used to let the bean container (CDI/JSF) create an instance of a bean on demand when referenced by expression

It seems that JSF 2.0 does not call "class level constraints". Quoting from an SO answer JSF 2.0 doesn't call class level validation constraints. From JSF validation: JSF 2 provides built-in integration with JSR-303 constraints. When you are using bean validation in your application, JSF automatically uses the constraints for beans that are referenced by UIInput values. The answer furthermore suggests using SeamFaces to validate the class-level constraints anyways. Unfortunately this is a non-option, since it introduces a somewhat massive dependency for just validating what should be validated

I have a spring boot project that has a CrudRepository, an Entity and a Controller. I am basically trying to persist an entity based on the data passed to the Controller. To do this, I am using spring-boot-starter-jpa . My Entity is annotated with JSR-303 annotations, which are checked in the controller before the data gets passed to the CrudRepository for persistence. Controller method: @RequestMapping(value = "users", method = { RequestMethod.POST }) public SuccessfulResponse<User> addUser(@Valid @RequestBody User user, BindingResult validation) { if (validation.hasErrors()) { throw new