public class Validation extends Object
There are three ways to bootstrap it:
ValidatorFactory
.
ValidatorFactory factory = Validation.buildDefaultValidatorFactory();In this case, the default validation provider resolver will be used to locate available providers.
The chosen provider is defined as followed:
ValidationProviderResolver
instance is used.ValidationProviderResolver
. The chosen
ValidationProvider
is then determined in the same way
as in the default bootstrapping case (see above).
Configuration<?> configuration = Validation .byDefaultProvider() .providerResolver( new MyResolverStrategy() ) .configure(); ValidatorFactory factory = configuration.buildValidatorFactory();
Optionally you can choose a custom ValidationProviderResolver
.
ACMEConfiguration configuration = Validation .byProvider(ACMEProvider.class) .providerResolver( new MyResolverStrategy() ) // optionally set the provider resolver .configure(); ValidatorFactory factory = configuration.buildValidatorFactory();
Note:
ValidatorFactory
object built by the bootstrap process should be cached
and shared amongst Validator
consumers.
Constructor and Description |
---|
Validation() |
Modifier and Type | Method and Description |
---|---|
static ValidatorFactory |
buildDefaultValidatorFactory()
Builds and returns a
ValidatorFactory instance based on the
default Jakarta Bean Validation provider and following the XML configuration. |
static GenericBootstrap |
byDefaultProvider()
Builds a
Configuration . |
static <T extends Configuration<T>,U extends ValidationProvider<T>> |
byProvider(Class<U> providerType)
Builds a
Configuration for a particular provider implementation. |
public static ValidatorFactory buildDefaultValidatorFactory()
ValidatorFactory
instance based on the
default Jakarta Bean Validation provider and following the XML configuration.
The provider list is resolved using the default validation provider resolver logic.
The code is semantically equivalent to
Validation.byDefaultProvider().configure().buildValidatorFactory()
.
ValidatorFactory
instanceNoProviderFoundException
- if no Jakarta Bean Validation provider was foundValidationException
- if a Jakarta Bean Validation provider was found but the
ValidatorFactory
cannot be builtpublic static GenericBootstrap byDefaultProvider()
Configuration
. The provider list is resolved
using the strategy provided to the bootstrap state.
Configuration<?> configuration = Validation .byDefaultProvider() .providerResolver( new MyResolverStrategy() ) .configure(); ValidatorFactory factory = configuration.buildValidatorFactory();The provider can be specified in the XML configuration. If the XML configuration does not exist or if no provider is specified, the first available provider will be returned.
Configuration
compliant with the bootstrap state providedpublic static <T extends Configuration<T>,U extends ValidationProvider<T>> ProviderSpecificBootstrap<T> byProvider(Class<U> providerType)
Configuration
for a particular provider implementation.
Optionally overrides the provider resolution strategy used to determine the provider.
Used by applications targeting a specific provider programmatically.
ACMEConfiguration configuration = Validation.byProvider(ACMEProvider.class) .providerResolver( new MyResolverStrategy() ) .configure();, where
ACMEConfiguration
is the
Configuration
sub interface uniquely identifying the
ACME Jakarta Bean Validation provider. and ACMEProvider
is the
ValidationProvider
implementation of the ACME provider.T
- the type of the Configuration
corresponding to this
ValidationProvider
U
- the type of the ValidationProvider
implementationproviderType
- the ValidationProvider
implementation typeConfiguration
sub interface implementationCopyright © 2021 JBoss by Red Hat. All rights reserved.