bean-validation

I am trying to put validation to a Spring Boot project. So I put @NotNull annotation to Entity fields. In controller I check it like this: @RequestMapping(value="", method = RequestMethod.POST) public DataResponse add(@RequestBody @Valid Status status, BindingResult bindingResult) { if(bindingResult.hasErrors()) { return new DataResponse(false, bindingResult.toString()); } statusService.add(status); return new DataResponse(true, ""); } This works. But when I make it with input List<Status> statuses , it doesn't work. @RequestMapping(value="/bulk", method = RequestMethod.POST) public List

Is JSR-303 also intended for method parameter validation? If so, is there any example on the web? The biggest challenge I'm facing is how to get a validator within each method. With Spring 3, doesn't it mean that I'd have to inject virtually every class with a LocalValidatorFactoryBean ? Thanks! This sounds like a use case for AOP (AspectJ). Write a pointcut for methods that are annotated with javax.validation.constraints.* , inject a validator into the aspect (probably using Spring) and use a @Before or @Around advice to perform the validation before method execution. Read AspectJ in Action

In Dropwizard I use @Valid annotations for my resource methods: public class Address { @NotNull String street ... } @Path("/address") @Produces(MediaType.APPLICATION_JSON) public class AddressResource { @POST public MyResponse addAddress(@Valid Address address) { if (address == null) { throw new WebApplicationException("address was null"); } ... } } On application start I register a custom WebApplicationExceptionMapper which handles WebApplicationExceptions . Thus, for addresses with the value null, the exception is thrown and handled in the mapper which generates a useful response. However,

I am trying to deploy a simple spring boot application that will expose some rest api and I use hibernate entity manager to manipulate entity objects. When I try to deploy this application to Oracle Weblogic 12c, I get the following exception: <Jan 11, 2016 6:20:14 PM BDT> <Error> <Console> <BEA-240003> <Administration Console encountered the following error: weblogic.application.ModuleException: java.lang.NoSuchMethodError: javax.validation.spi.ConfigurationState.getParameterNameProvider()Ljavax/validation/ParameterNameProvider; at weblogic.application.internal.ExtensibleModuleWrapper.start

here is my formbean:- public class LoginFormBean { @NotEmpty private String userId; @NotEmpty private String password; public String getUserId() { return userId; } public void setUserId(String userId) { this.userId = userId; } public String getPassword() { return password; } public void setPassword(String pass) { this.password = pass; } } and in my message.properties file i write:- NotEmpty={0} must not empty. It shows me error message as: userId must not empty. and password must not empty. But i want to show error message as User Id must not empty. or 'Password must not empty.' I know i can

Aloha hey! I already use JPA annotations, now I'd like to use JSR-303 annotations to validate attributes as well. My questions is, how well do they interact with each other? If I use @Basic(optional=false) or @NotNull , will I still have to use nullable=false etc.? I haven't decided which validator implementation to use, e.g. hibernate-validator or oVal (You may also suggest others. I know that oVal is not a JSR-303 implementation, but it maps most annotations ). oVal manual (see above) states that certain JPA annotations will be translated into oVal annotations as well. Hibernate-validator

I use JSR-303 bean validation and Spring 3 and I need to provide different values for the annotation depending on the use-case. For example, the value of min parameter in @Size(min=?) must be 1 for some validation and 5 for another case and I want to read this values from a properties file. I know the message parameter can be read from ValidationMessages.properties file if provided as a key but what about the other parameter? As outlined by dpb you can use validation groups to specify the same constraint with different attribute values. If you're working with Hibernate Validator as BV