Uses of Package
de.knightsoftnet.validators.shared

Package
Description
JSR-303/JSR-349 annotations to check bean entries (interfaces).
JSR-303/JSR-349/JSR-380 annotations to check bean entries (implementations).
  • Class
    Description
    The annotated element size must be exactly match size1 or size2.
    Supported types are Strings null elements are considered valid.
    With the following options separator characters can be removed before size is checked: ignoreWhiteSpaces (true/false, default false) ignoreMinus (true/false, default false) ignoreSlashes (true/false, default false)
    The annotated element size must be between the specified boundaries (included).
    Supported types are Strings, other Objects are transfered to Strings, null elements are considered valid.
    With the following options separator characters can be removed before size is checked: ignoreWhiteSpaces (true/false, default false) ignoreMinus (true/false, default false) ignoreSlashes (true/false, default false)
  • Class
    Description
    The annotated Date must be minYears or more in the past.
    Supported types are Dates, null elements are considered valid.
    The annotated element size must be exactly match size1 or size2.
    Supported types are Strings null elements are considered valid.
    With the following options separator characters can be removed before size is checked: ignoreWhiteSpaces (true/false, default false) ignoreMinus (true/false, default false) ignoreSlashes (true/false, default false)
    The annotated bean must contain three properties: country code (option fieldCountryCode) iban (option fieldIban) bic (option fieldBic) The country codes of iban and bic are checked against the country code for validity.
    Supported types are beans, null elements are considered valid.
    If allowLowerCaseCountryCode is set to true, lower case country codes are accepted.
    The annotated element must be a valid BIC (Business Identifier Code in the past also known as Bank Identifier Code).
    Supported types are Strings, other Objects are transfered to Strings, null elements are considered valid.
    If ignoreWhiteSpaces is set to true, whitespaces are removed before test is done.
    It's a formal test, against format definition, size and SWIFT country list.
    There is no test of validity of the BIC!
    The annotated element must be a valid BIC (Business Identifier Code in the past also known as Bank Identifier Code).
    Supported types are Strings, other Objects are transfered to Strings, null elements are considered valid.
    If ignoreWhiteSpaces is set to true, whitespaces are removed before test is done.
    It's a formal test, against format definition, size and SWIFT country list.
    There is no test of validity of the BIC!
    The annotated element must be a valid credit card number.
    Supported types are Strings, other Objects are transfered to Strings, null elements are considered valid.
    There are format, size and LUN checksum tests by apache commons validation routines.
    There are no tests for credit card validity!
    The annotated element must be a valid eMail.
    Supported types are Strings, other Objects are transfered to Strings, null elements are considered valid.
    There are format tests, domain validity tests, and size checks by apache commons validation routines.
    The annotated bean must contain at least two properties: a field to compare (option field1) another field to compared (option field2) add the error to field1 (option addErrorToField1, default true) add the error to field2 (option addErrorToField2, default true) the eMail entry of field1 must have the same domain as the eMail entry of field2.
    Supported types are beans, null elements are considered valid.
    The annotated bean must contain at least two properties: a field that has to be checked (option field) a field which entry is compared against a value (option fieldCompare and valueCompare) if the entry of fieldCompare matches valueCompare, field must be empty (null or "").
    Supported types are beans, null elements are considered valid.
    The annotated bean must contain at least two properties: a field that has to be checked (option field) a field which entry is compared (option fieldCompare) if the entry of fieldCompare is empty (null or ""), field must be also empty (null or "").
    Supported types are beans, null elements are considered valid.
    The annotated bean must contain at least two properties: a field that has to be checked (option field) a field which entry is compared (option fieldCompare) if the entry of fieldCompare is not empty (null or ""), field must be empty (null or "").
    Supported types are beans, null elements are considered valid.
    The annotated element must be a valid Global Location Number (until 2009 known as International Location Number).
    Supported types are Strings, other Objects are transfered to Strings, null elements are considered valid.
    There are numeric, size and checksum tests by apache commons validation routines.
    The annotated element must be a valid Global Trade Item Number (until 2009 known as European Article Number) in the long (13 digits) or short (8 digits) format.
    Supported types are Strings, other Objects are transfered to Strings, null elements are considered valid.
    There are numeric, size and checksum tests by apache commons validation routines.
    The annotated element must be a valid Global Trade Item Number (until 2009 known as European Article Number) in the long (13 digits) format.
    Supported types are Strings, other Objects are transfered to Strings, null elements are considered valid.
    There are numeric, size and checksum tests by apache commons validation routines.
    The annotated element must be a valid Global Trade Item Number (until 2009 known as European Article Number) in the short (8 digits) format.
    Supported types are Strings, other Objects are transfered to Strings, null elements are considered valid.
    There are numeric, size and checksum tests by apache commons validation routines.
    The annotated element must be a valid International Bank Account Number.
    Supported types are Strings, other Objects are transfered to Strings, null elements are considered valid.
    The annotated element must be a valid International Bank Account Number.
    Supported types are Strings, other Objects are transfered to Strings, null elements are considered valid.
    The annotated element must be a valid International Standard Book Number in the long (13 digits) or short (10 digits) format.
    Supported types are Strings, other Objects are transfered to Strings, null elements are considered valid.
    The annotated element must be a valid International Standard Book Number in the short (10 digits) format.
    Supported types are Strings, other Objects are transfered to Strings, null elements are considered valid.
    The annotated element must be a valid International Standard Book Number in the short (10 digits) format.
    Supported types are Strings, other Objects are transfered to Strings, null elements are considered valid.
    The annotated element must be a valid International Standard Book Number in the long (13 digits) format.
    Supported types are Strings, other Objects are transfered to Strings, null elements are considered valid.
    The annotated element must be a valid International Standard Book Number in the long (13 digits) format.
    Supported types are Strings, other Objects are transfered to Strings, null elements are considered valid.
    The annotated element must be a valid International Standard Book Number in the long (13 digits) or short (10 digits) format.
    Supported types are Strings, other Objects are transfered to Strings, null elements are considered valid.
    The annotated element must be a valid International Securities Identification Number.
    Supported types are Strings, other Objects are transfered to Strings, null elements are considered valid.
    There are format, size, SEPA country and checksum tests by apache commons validation routines.
    The annotated bean must contain exact three properties: a field that has to be checked (option field1) a field which entry is compared (option field2) the minimum levenshtein distance both field entries must have (option minDistance) add the error to field1 (option addErrorToField1, default true) add the error to field2 (option addErrorToField2, default true) The Levenshtein distance between the entry of fieldCompare and field is calculated, it must be equal or greater then the value of minDistance. not be empty (null or "").
    The annotated element must contain only characters which are allowed in the given charset.
    Supported types are Strings, other Objects are transfered to Strings, null elements are considered valid.
    The charset must be given as parameter.
    The annotated bean must contain at least two properties: a field to compare (option field1) another field to compared (option field2) add the error to field1 (option addErrorToField1, default true) add the error to field2 (option addErrorToField2, default false) the entry of field1 must be bigger then entry of field2, can be used e.g. for date or number "from"/"to" fields.
    Supported types are beans, null elements are considered valid.
    The fields must implement Comparable!
    The annotated bean must contain at least two properties: a field to compare (option field1) another field to compared (option field2) add the error to field1 (option addErrorToField1, default true) add the error to field2 (option addErrorToField2, default false) the entry of field1 must be bigger or equal then entry of field2, can be used e.g. for date or number "from"/"to" fields.
    Supported types are beans, null elements are considered valid.
    The fields must implement Comparable!
    The annotated bean must contain at least two properties: a field to compare (option field1) another field to compared (option field2) add the error to field1 (option addErrorToField1, default true) add the error to field2 (option addErrorToField2, default true) the entry of field1 must be equal to the entry of field2, can be used e.g. for password and password repeat fields.
    Supported types are beans, null elements are considered valid.
    The annotated bean must contain at least four properties: a field to compare (option field1) another field to compared (option field2) a field which entry is compared against a value (option fieldCompare and valueCompare) add the error to field1 (option addErrorToField1, default true) add the error to field2 (option addErrorToField2, default true) the entry of field1 must be equal to the entry of field2 when the entry of fieldCompare has the value valueCompare, can be used e.g. for password and password repeat fields.
    Supported types are beans, null elements are considered valid.
    The annotated bean must contain at least two properties: a field to compare (option field1) another field to compared (option field2) add the error to field1 (option addErrorToField1, default true) add the error to field2 (option addErrorToField2, default false) the entry of field1 must be smaller then entry of field2, can be used e.g. for date or number "from"/"to" fields.
    Supported types are beans, null elements are considered valid.
    The fields must implement Comparable!
    The annotated bean must contain at least two properties: a field to compare (option field1) another field to compared (option field2) add the error to field1 (option addErrorToField1, default true) add the error to field2 (option addErrorToField2, default false) the entry of field1 must be smaller or equal then entry of field2, can be used e.g. for date or number "from"/"to" fields.
    Supported types are beans, null elements are considered valid.
    The fields must implement Comparable!
    The annotated bean must contain at least two properties: a field to compare (option field1) another field to compared (option field2) add the error to field1 (option addErrorToField1, default true) add the error to field2 (option addErrorToField2, default true) the entry of field1 must not be equal to the entry of field2, can be used e.g. for password old and password new fields.
    Supported types are beans, null elements are considered valid.
    The annotated bean must contain at least two properties: a field to compare (option field1) another field to compared (option field2) a field which entry is compared against a value (option fieldCompare and valueCompare) add the error to field1 (option addErrorToField1, default true) add the error to field2 (option addErrorToField2, default true) the entry of field1 must not be equal to the entry of field2 when the entry of fieldCompare has the value valueCompare, can be used e.g. for password old and password new fields.
    Supported types are beans, null elements are considered valid.
    The annotated element must not be null or empty after strip.
    The annotated bean must contain at least three properties: a field that has to be checked (option field) a field that has alternate to be checked (option fieldAlternate) a field which entry is compared against a value (option fieldCompare and valueCompare) if the entry of fieldCompare matches valueCompare, field or alternate fieldAlternate must not be empty (null or "").
    Supported types are beans, null elements are considered valid.
    The annotated bean must contain at least three properties: a field that has to be checked (option field) a field that has alternate to be checked (option fieldAlternate) a field which entry is compared (option fieldCompare) if the entry of fieldCompare is empty (null or ""), field or alternate fieldAlternate must not be empty (null or "").
    Supported types are beans, null elements are considered valid.
    The annotated bean must contain at least three properties: a field that has to be checked (option field) a field that has alternate to be checked (option fieldAlternate) a field which entry is compared (option fieldCompare) if the entry of fieldCompare is not empty (null or ""), field or alternate fieldAlternate must not be empty (null or "").
    Supported types are beans, null elements are considered valid.
    The annotated bean must contain at least two properties: a field that has to be checked (option field) a field which entry is compared against a value (option fieldCompare and valueCompare) if the entry of fieldCompare matches valueCompare, field must not be empty (null or "").
    Supported types are beans, null elements are considered valid.
    The annotated bean must contain at least two properties: a field that has to be checked (option field) a field which entry is compared (option fieldCompare) if the entry of fieldCompare is empty (null or ""), field must not be empty (null or "").
    Supported types are beans, null elements are considered valid.
    The annotated bean must contain at least two properties: a field that has to be checked (option field) a field which entry is compared (option fieldCompare) if the entry of fieldCompare is not empty (null or ""), field must also not be empty (null or "").
    Supported types are beans, null elements are considered valid.
    The annotated bean must contain at least two properties: a field that has to be checked (option field) a array of fields and entries to be compared (option otherFieldValueMapping) if the entries of otherFieldValueMapping.fieldCompare matches one of the corresponding entries in otherFieldValueMapping.valueCompare (array of possible values), field must not be empty (null or "").
    Supported types are beans, null elements are considered valid.
    The annotated element must be a valid password.
    Supported types are Strings, other Objects are transfered to Strings, null elements are considered valid.
    There are the following rules checked (with minRules parameter the number rules can be defined that have to be fulfilled): lowercase upercase digits special character Using blacklist you can give a comma separated list of words which are not allowed to be part of the password.
    The annotated element must be a valid phone number format.
    Supported types are Strings, other Objects are transfered to Strings, null elements are considered valid.
    The annotated element must be a valid phone number format.
    Supported types are Strings, other Objects are transfered to Strings, null elements are considered valid.
    The annotated bean must contain two properties: country code (option fieldCountryCode) postal code/zip (option fieldPostalCode) The postal code is checked against country specific rules for validity.
    Supported types are beans, null elements are considered valid.
    If allowLowerCaseCountryCode is set to true, lower case country codes are accepted.
    The annotated element must be a valid regular expression.
    Supported types are Strings, other Objects are transfered to Strings, null elements are considered valid.
    The annotated element size must be between the specified boundaries (included).
    Supported types are Strings, other Objects are transfered to Strings, null elements are considered valid.
    With the following options separator characters can be removed before size is checked: ignoreWhiteSpaces (true/false, default false) ignoreMinus (true/false, default false) ignoreSlashes (true/false, default false)
    The annotated bean must contain two properties: country code (option fieldCountryCode) tax number (option fieldTaxNumber) The Tax Number is checked against country specific rules for validity.
    The annotated bean must contain two properties: country code (option fieldCountryCode) tin (option fieldTin) The Tax Identification Number (TIN) is checked against country specific rules for validity.
    The annotated element must be a valid url.
    Supported types are Strings, other Objects are transfered to Strings, null elements are considered valid.
    There are format tests, domain validity tests, and size checks by apache commons validation routines.
    The annotated bean must contain two properties: country code (option fieldCountryCode) vat id (option fieldVatId) The vat id is checked against country specific rules for validity.