public class EmailValidator extends Object implements ConstraintValidator<Email,CharSequence>
The specification of a valid email can be found in RFC 2822 and one can come up with a regular expression matching all valid email addresses as per specification. However, as this article discusses it is not necessarily practical to implement a 100% compliant email validator. This implementation is a trade-off trying to match most email while ignoring for example emails with double quotes or comments.
| Constructor and Description |
|---|
EmailValidator() |
| Modifier and Type | Method and Description |
|---|---|
void |
initialize(Email annotation)
Initializes the validator in preparation for
ConstraintValidator.isValid(Object, ConstraintValidatorContext) calls. |
boolean |
isValid(CharSequence value,
ConstraintValidatorContext context)
Implements the validation logic.
|
public void initialize(Email annotation)
ConstraintValidatorConstraintValidator.isValid(Object, ConstraintValidatorContext) calls.
The constraint annotation for a given constraint declaration
is passed.
This method is guaranteed to be called before any use of this instance for validation.
The default implementation is a no-op.
initialize in interface ConstraintValidator<Email,CharSequence>annotation - annotation instance for a given constraint declarationpublic boolean isValid(CharSequence value, ConstraintValidatorContext context)
ConstraintValidatorvalue must not be altered.
This method can be accessed concurrently, thread-safety must be ensured by the implementation.
isValid in interface ConstraintValidator<Email,CharSequence>value - object to validatecontext - context in which the constraint is evaluatedfalse if value does not pass the constraintCopyright © 2018 JBoss by Red Hat. All rights reserved.