public final class EmailFormatSpecifier extends FormatSpecifier
email format specification.
Note: even though the RFC covering email addresses does not require that
emails have a domain part, this implementation requires that they have one
by default (this is more in line with user expectations). You can enforce
strict RFC compliance by setting the ValidationFeature.STRICT_RFC_CONFORMANCE validation feature before building
your schema factory.
ValidationFeature| Modifier and Type | Field and Description |
|---|---|
private static FormatSpecifier |
instance |
| Modifier | Constructor and Description |
|---|---|
private |
EmailFormatSpecifier() |
| Modifier and Type | Method and Description |
|---|---|
void |
checkValue(String fmt,
ValidationContext ctx,
ValidationReport report,
JsonNode instance)
Abstract method implemented by all specifiers
|
static FormatSpecifier |
getInstance() |
newMsg, validateprivate static final FormatSpecifier instance
public static FormatSpecifier getInstance()
public void checkValue(String fmt, ValidationContext ctx, ValidationReport report, JsonNode instance)
FormatSpecifierIt is only called if the value type is one expected by the
specifier, see FormatSpecifier.validate(String, ValidationContext,
ValidationReport, JsonNode).
checkValue in class FormatSpecifierfmt - the format specifier namectx - the validation contextreport - the validation reportinstance - the value to validateCopyright © 2012. All Rights Reserved.