bean-validation

I'm creating a JSF 2-application and I'm trying to use form validation in the bean instead of the faces-page. I'd also like to use a .properties file to store the messages. I looked at this question but I don't think I have the properties-file set up correctly. Let's say I have a bean called User in a package called 'dev': @ManagedBean @SessionScoped public class User implements Serializable { @Pattern(pattern=".+@.+\\.[a-z]+", message="{dev.User.emailAddress}") private String emailAddress; // getter/setter } I've also created a file 'ValidationMessages.properties' in WEB-INF/classes (I'm

How to create a validator restrictions for more fields through annotation in spring 4.* for example @UniqueValidator @Entity @Table(name = "persons") @UniqueValidator(message="Peson already exist",columns={"name","lastName"}) public class { @Column private String name; @Column private String lastName; } roughly speaking.. select ... from persons where name='qwerty' and lastName='asdfgh' Here's one way to do it in Spring MVC and JSR 303 validation: Create a constraint annotation: package com.awgtek.model.validation; import java.lang.annotation.Documented; import java.lang.annotation.ElementType

Given the following classes and interfaces class A{ @NotNull(groups=Section1.class) private String myString } interface All{} interface Section1 extends All {} When calling A a = new A(); validator.validate(a,All.class); I would expect that it should be invalid since myString is null and it's notNull group extends All but it does not. Note that i'm using the Hibernate impl (4.0.2.GA) of the validator Your expectations are backwards from what the specification requires. From the spec (page 27 on the PDF): For a given interface Z, constraints marked as belonging to the group Z (i.e. where the

I have a simple bean, i.e.: public class MyBean { private boolean selected; private String someString; ... } So if selected is true, I want someString to be @NotNull etc. . Any hints, links how to achieve this behaviour? Thanks Jonny You could do this by annotating MyBean with a custom validator, for example: @ValidMyBean public class MyBean { private boolean selected; private String someString; ... } ValidMyBean: @Target({ ElementType.FIELD }) @Retention(RetentionPolicy.RUNTIME) @Constraint(validatedBy = MyBeanValidator.class) public @interface ValidMyBean { boolean allViolationMessages()

I am trying to get a bean injected into a custom ConstraintValidator . I have come across some things: CDI is supported in validation-api-1.1.0 (Beta available) Hibernate Validator 5 seems to implement validation-api-1.1.0 (Alpha available) Use Seam validation module Use Spring's LocalValidatorFactoryBean The last one seems most appropriate for my situation since we're already using Spring (3.1.3.Release). I have added the validator factory to the XML application context and annotations are enabled: <beans xmlns="http://www.springframework.org/schema/beans" xmlns:xsi="http://www.w3.org/2001

I was writing a Spring Boot Application. I wanted to know does Spring Boot automatically resolve message keys in javax and hibernate validation annotations. For example: @NotEmpty(message = "${message.key}") String name; I have provided @PropertySource in my application with message properties file and file is also in my classpath. The keys are resolving with @Value but they are not being resolved in validation annotations. What could be the reason for this? Do I need configure a message source bean? Because I have seen examples working without configuring the message source bean. Miloš