This content has been marked as final. Show 1 reply
In JSF, you have to define validation logic for every input component to be validated. In several cases this means you must violate the "Don't Repeat Yourself" (DRY) principle. A simple example is a property of an entity that is specified as required in JPA. Even though this information is already available in the model, you also have to specify that the input component bound to the mentioned property is required, by setting the required attribute to true. If the model changes, you have to go though all pages of your JSF application and change the corresponding components.
Developers could also resolve this restriction using HibernateValidation support starting from RichFaces 3.2.2. Could be used with or without Seam.