Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Avoid calling UIInput.setValid(false) on all unmatched components when using <o:validateBean showMessageFor="@violating" .../> #352
I have a use-case where a bean is being validated using
I'd like to eliminate step 5 since val2 is actually valid.
I'd also like to eliminate step 6 since redundantly, the generic, unlabeled "may not be null" message from CV2 gets rendered by the h:messages component, just below the labeled message for CV1, further confusing the user.