bean-validation

Since springmvc 3.x now supports jsr303 and old spring style validator, i want to mix them in my sample apps. But there is only one method enabled for a specified controller, is that the limit of spring framework or JSR standard? Here is my sample code. User.java, stands for the domain model, uses JSR303 for validation. public class User{ @Size(max = 16, message = "user loginId max-length is 16") private String loginId; //omit getter and setter } UserValidator.java, implements the org.springframework.validation.Validator interface to support user validation. public class UserValidator

I have the next issue while working with jsr303: i have field annotated the next way: @NotEmpty(message = "Please specify your post code") @PostCode(message = "Your post code is incorrect") private String postCode; But I need to check @PostCode only if field passed the validation for @NotEmpty. How can I checking for tese two annotations? Thanks in advance You can use validation groups to execute validations group-wise. For details, see section 3.4. Group and group sequence in JSR-303 . In your sample you would do something like: @NotEmpty(message = "Please specify your post code") @PostCode

I was checking list of available constraints in javax.validation package and I noticed that there is an annotation @Null which force the field to be null. I do not understand what is point of adding it to my field if I already know it should be null. For example look at this class: public class MyClass{ @NotNull private String myString1; @Null private String myString2; // getter setters... } @NotNull completely makes sense. I do not expect myString1 to be null. but @Null makes myString2 useless. What is point of having a field which should always be null. You may want to use @Null in

so first of all i could not think of a better title for this question so i'm open for changes. I am trying to validate a bean using the bean validation mechanism (JSR-380) with spring boot. So i got a controller like this: @Controller @RequestMapping("/users") class UserController { @PostMapping fun createUser(@Validated user: User, bindingResult: BindingResult): ModelAndView { return ModelAndView("someview", "user", user) } } with this being the User class written in kotlin: data class User( @field:NotEmpty var roles: MutableSet<@NotNull Role> = HashSet() ) and this being the test: @Test

In JSF 2.3, I have an h:inputText to edit a Double value, which has in addition Bean-Validation constraints. The h:inputText has a f:convertNumber . When submitting the form, this leads to a ClassCastException (see below). So, it seems, that f:convertNumber produces a Long which then, could not be converted to Double to validate the @DecimalMin constraint, right? In JSF 2.2 this worked as expected, the problem occured after upgrading to JSF 2.3. Does anybody has any ideas what could be the problem? I could reproduce this in WildFly 15.0.1 with the following minimal example with just one