Java EE 8 By Example
  • Introduction
  • Overview
    • Example Codes
  • JSF 2.3
    • Activating CDI in JSF 2.3
    • Run applications in JSF 2.2 compatible mode
    • CDI alignment
    • CDI compatible @ManagedProperty
    • Inject support in Converter, Validator and Behavor
    • Websocket support
    • UIData improvements
    • Class level bean validation with f:valdiateWholeBean
    • Java 8 DateTime support
    • PostRenderViewEvent: publising events after view is rendered
    • Search expression framework
  • CDI 2.0
    • Java SE support
    • Event Priority
    • Async Events
    • Register Beans dynamicially
    • Configurators and Intercept Producers
  • JPA 2.2
    • Java 8 Datetime support
    • Return Stream based result from Query
    • More CDI Alignments
  • JSON-B 1.0
  • JSON-P 1.1
  • Bean Validation 2.0
  • JAXRS 2.1
    • Async improvements
    • Server Sent Event
    • Reactive Client
  • Java EE Security API 1.0
    • HttpAuthenticationMechanism
    • IdentityStore
    • SecurityContext
  • Servlet 4.0
    • Server Push
    • Runtime Discovery of Servlet Mappings
    • Http Trailer
  • MVC 1.0
    • Getting started with MVC
    • Handling form submission
    • Exception handling and form validation
    • Processing PUT and DELETE methods
    • Page navigation
    • MVC and CDI
    • Security
    • Bean parameter conversion
    • View engine
Powered by GitBook
On this page

Was this helpful?

  1. JSF 2.3

Class level bean validation with f:valdiateWholeBean

PreviousUIData improvementsNextJava 8 DateTime support

Last updated 4 years ago

Was this helpful?

JSF provides a f:validateBean which bridges Bean Validation to JSF, why we need another f:validateWholeBean?

This is explained in details in the of f:validateWholeBean.

Support multi-field validation by enabling class-level bean validation on CDI based backing beans. This feature causes a temporary copy of the bean referenced by the value attribute, for the sole purpose of populating the bean with field values already validated by and then performing class-level validation on the copy. Regardless of the result of the class-level validation, the copy is discarded.

in another word, it provides the capability of cross fields validation.

A good example is password matching check in a signup page, we have to make sure the values in password field and password confirm field are equivalent.

Create a bean validation annotation @Password.

@Constraint(validatedBy=PasswordValidator.class)
@Target(TYPE)
@Retention(RUNTIME)
@interface Password {

    String message() default "Password fields must match";
    Class[] groups() default {};
    Class[] payload() default {};
}

Constraint declares which validator will handle this annotation, here it is PasswordValidator.

public class PasswordValidator implements ConstraintValidator<Password, PasswordHolder> {

  @Override
  public void initialize(Password constraintAnnotation) { }

  @Override
  public boolean isValid(PasswordHolder value, ConstraintValidatorContext context) {
    boolean result;

    result = value.getPassword1().equals(value.getPassword2());

    return result;
  }

}

ConstraintValidator accept two parameters, the validator annotation, and the type(PasswordHolder) will be applied.

PasswordHolder is an interface which holds the values of two password fields.

public interface PasswordHolder {

    String getPassword1();
    String getPassword2();  
}

Create a backing bean to put all together.

@Named
@RequestScoped
@Password(groups = PasswordValidationGroup.class)
public class BackingBean implements PasswordHolder, Cloneable {

    private String password1;

    private String password2;

    public BackingBean() {
        password1 = "";
        password2 = "";
    }

    @Override
    protected Object clone() throws CloneNotSupportedException {
        BackingBean other = (BackingBean) super.clone();
        other.setPassword1(this.getPassword1());
        other.setPassword2(this.getPassword2());
        return other;
    }

    @NotNull(groups = PasswordValidationGroup.class)
    @Size(max = 16, min = 8, message = "Password must be between 8 and 16 characters long",
            groups = PasswordValidationGroup.class)
    @Override
    public String getPassword1() {
        return password1;
    }

    public void setPassword1(String password1) {
        this.password1 = password1;
    }

    @NotNull(groups = PasswordValidationGroup.class)
    @Size(max = 16, min = 8, message = "Password must be between 8 and 16 characters long",
            groups = PasswordValidationGroup.class)
    @Override
    public String getPassword2() {
        return password2;
    }

    public void setPassword2(String password2) {
        this.password2 = password2;
    }

}

We apply Password validation on the backingBean, it is a class level validation.

Create a simple facelets template.

<h:panelGroup id="messageFromInputBox">
    <h:messages />
</h:panelGroup>
<h:form>
    <h:panelGrid columns="2">

        <h:outputText value="Password" />  
        <h:inputSecret id="password1" value='#{backingBean.password1}' required="true">
            <f:validateBean validationGroups="javax.validation.groups.Default,com.hantsylabs.example.ee8.jsf.PasswordValidationGroup" />
        </h:inputSecret>

        <h:outputText value="Password again" /> 
        <h:inputSecret id="password2" value='#{backingBean.password2}' rendered="true">
            <f:validateBean validationGroups="javax.validation.groups.Default,com.hantsylabs.example.ee8.jsf.PasswordValidationGroup" />
        </h:inputSecret>

    </h:panelGrid>

    <f:validateWholeBean value='#{backingBean}' 
                         validationGroups="com.hantsylabs.example.ee8.jsf.PasswordValidationGroup" />
    <div>
        <h:commandButton 
            id="validtePassword" 
            value="Validate Password">
            <f:ajax execute="@form" render=":messageFromInputBox" />
        </h:commandButton>
    </div>
</h:form>

f:validateWholeBean accept a value attribute to set the backing bean.

NOTE, we use a PasswordValidationGroup group to differentiate varied validations.

PasswordValidationGroup is just an interface.

public interface PasswordValidationGroup {

}

Try to input passwords, if its length is less than 8, submit form, it will display erros like.

If the length is valid, and the two password are not matched, it will trigger the @Password validator.

Run the project on Glassfish v5, open your browser and navigate to .

Grab the from my GitHub account, and have a try.

VDL docs
http://localhost:8080/jsf-validwholebean/
source codes
length validation error
password validator error