Best what you can do is to grab the other UIInput component by UIViewRoot#findComponent() inside the validate() method and then determine the submitted value by either UIInput#getSubmittedValue() (when it occurs after the currently validated component in the component tree) or UIInput#getValue() (when it occurs before the current component and thus is already validated). E.g. public … Read more
Now, you don’t need to use FormBuilder and all this complicated valiation angular stuff. I put more details from this (Angular 2.0.8 – 3march2016): https://github.com/angular/angular/commit/38cb526 Example from repo : <input [ngControl]=”fullName” pattern=”[a-zA-Z ]*”> I test it and it works 🙂 – here is my code: <form (ngSubmit)=”onSubmit(room)” #roomForm=’ngForm’ > … <input id=’room-capacity’ type=”text” class=”form-control” [(ngModel)]=’room.capacity’ … Read more
Here’s a free and sort of “outside the box” way to do it. Not 100% perfect, but it should reject blatantly non-existent addresses. Submit the entire address to Google’s geocoding web service. This service attempts to return the exact coordinates of the location you feed it, i.e. latitude and longitude. In my experience if the … Read more
There’s physically only one UIInput component whose state changes depending on the current iteration round of UIRepeat. It’s available by just its client ID without the UIRepeat index: findComponent(“formId:inputId”) (the UIRepeat index is only of significance in the client side). However, when the component is programmatically been accessed outside the context of UIRepeat this way, … Read more
The PrimeFaces ajax response puts an args object in the scope which has a validationFailed property. You could just make use of it. oncomplete=”if (args && !args.validationFailed) PF(‘editDialog’).hide()” (the args precheck is necessary to not cause a JS error when an exception is thrown during request) You could refactor it to a reusable JS function … Read more
This is probably not the answer you’re looking, but I just noticed Validation has the following methods /** Run a disjunction function and back to validation again. Alias for `@\/` */ def disjunctioned[EE, AA](k: (E \/ A) => (EE \/ AA)): Validation[EE, AA] = k(disjunction).validation /** Run a disjunction function and back to validation again. … Read more
Based on the answer of santiagomaldonado I have created a generic ValidatorFn that can be used in multiple Reactive Forms with a dynamic return value. export class DateValidators { static dateLessThan(dateField1: string, dateField2: string, validatorField: { [key: string]: boolean }): ValidatorFn { return (c: AbstractControl): { [key: string]: boolean } | null => { const … Read more
That’s normal and natural behaviour and not JSF specific. A blank space may be perfectly valid input. The required=”true” only kicks in on empty inputs, not in filled inputs. In JSF you can however just create a Converter for String class to automatically trim the whitespace. @FacesConverter(forClass=String.class) public class StringTrimmer implements Converter { @Override public … Read more
The simplest way would be to set the validatorMessage=”my custom message” attribute in the <h:inputText> tag. For a more advanced way read this article Customize validation error message in JSF 2.0 And here a complete Reference to all available message that you can override in JSF 2.0.x
HTML5 + JSF 2.2+ If you’re using HTML5 and JSF 2.2+, specify it as a passthrough attribute. <html … xmlns:a=”http://xmlns.jcp.org/jsf/passthrough”> <h:inputTextarea value=”#{bean.text}” a:maxlength=”2000″ /> HTML4 If you’re on HTML4, then it’s already not supported by HTML itself. It’s only supported on <input> element, not on <textarea> element. That’s also why there’s no such attribute on … Read more