But this can cause some problems, at least, it is causing problems for me now I have two text fields.The only validation rule is that one of them has to have a value. Because if I set allow Blank to true, then extjs will return true, without running my validator function.The Forum adopted EV Guidelines for issuing code signing certificates, and in 2011 adopted the Baseline Requirements for the Issuance and Management of Publicly-Trusted SSL/TLS Certificates to improve accreditation and approval schemes for all applicants who request that their self-signed root certificates be embedded as trust anchors in software and to extend common standards for issuing SSL/TLS certificates beyond EV to include all Domain-validated (DV) and Organization-Validated (OV) certificates.read more The Forum has also adopted a set of “Network and Certificate System Security Requirements” applicable to all publicly trusted CAs with the intent that all such CAs and Delegated Third Parties be audited for conformity once they have been incorporated as mandatory requirements (if not already mandatory requirements) in browser root programs or existing audit criteria.So, I have two textfields, and what I'd like to achieve is this: They are valid, if one of them contains some string.Like this: field1: some text field2: (empty) OR field1: (empty) field2: some text So, let's assume, that I have set both of them to allow blank (allow Blank = true) In this case, if both of them are empty, they will be valid, since this: will return true immediately, not running my validator function.
Does anyone have a simple example of validating the input for a text field in a org.eclipse.jface.wizard. (To prevent the user from going to the next page) The example I am following is
EV certificates are issued after extended steps to verify the identity of the entity behind the domain receiving the certificate.
Internet browser software displays enhanced indication of that identity by changing the appearance of its display (i.e.
(This will return false immediately: ) ok, after reading through the API docs it does state that the custom validator only gets executed if any present basic validators return true.
since you need to take into account two different fields in your validator, the basic validators can no longer help and must always return true (or not be present).