public class ValidatorContextImpl extends Object implements HibernateValidatorContext
Constructor and Description |
---|
ValidatorContextImpl(ValidatorFactoryImpl validatorFactory) |
public ValidatorContextImpl(ValidatorFactoryImpl validatorFactory)
public HibernateValidatorContext messageInterpolator(MessageInterpolator messageInterpolator)
messageInterpolator
in interface ValidatorContext
messageInterpolator
in interface HibernateValidatorContext
public HibernateValidatorContext traversableResolver(TraversableResolver traversableResolver)
traversableResolver
in interface ValidatorContext
traversableResolver
in interface HibernateValidatorContext
public HibernateValidatorContext constraintValidatorFactory(ConstraintValidatorFactory factory)
constraintValidatorFactory
in interface ValidatorContext
constraintValidatorFactory
in interface HibernateValidatorContext
public HibernateValidatorContext parameterNameProvider(ParameterNameProvider parameterNameProvider)
parameterNameProvider
in interface ValidatorContext
parameterNameProvider
in interface HibernateValidatorContext
public HibernateValidatorContext clockProvider(ClockProvider clockProvider)
clockProvider
in interface ValidatorContext
clockProvider
in interface HibernateValidatorContext
public HibernateValidatorContext addValueExtractor(ValueExtractor<?> extractor)
addValueExtractor
in interface ValidatorContext
addValueExtractor
in interface HibernateValidatorContext
public HibernateValidatorContext failFast(boolean failFast)
HibernateValidatorContext
failFast
in interface HibernateValidatorContext
failFast
- true
to enable fail fast, false
otherwise.this
following the chaining method patternpublic HibernateValidatorContext allowOverridingMethodAlterParameterConstraint(boolean allow)
HibernateValidatorContext
ConstraintDefinitionException
.
The default value is false
, i.e. do not allow.
See Section 4.5.5 of the JSR 380 specification, specifically
"In sub types (be it sub classes/interfaces or interface implementations), no parameter constraints may be declared on overridden or implemented methods, nor may parameters be marked for cascaded validation. This would pose a strengthening of preconditions to be fulfilled by the caller."
allowOverridingMethodAlterParameterConstraint
in interface HibernateValidatorContext
allow
- flag determining whether validation will allow overriding to alter parameter constraints.this
following the chaining method patternpublic HibernateValidatorContext allowMultipleCascadedValidationOnReturnValues(boolean allow)
HibernateValidatorContext
false
, i.e. do not allow.
See Section 4.5.5 of the JSR 380 specification, specifically
"One must not mark a method return value for cascaded validation more than once in a line of a class hierarchy. In other words, overriding methods on sub types (be it sub classes/interfaces or interface implementations) cannot mark the return value for cascaded validation if the return value has already been marked on the overridden method of the super type or interface."
allowMultipleCascadedValidationOnReturnValues
in interface HibernateValidatorContext
allow
- flag determining whether validation will allow multiple cascaded validation on return values.this
following the chaining method patternpublic HibernateValidatorContext allowParallelMethodsDefineParameterConstraints(boolean allow)
HibernateValidatorContext
ConstraintDefinitionException
. The
default value is false
, i.e. do not allow.
See Section 4.5.5 of the JSR 380 specification, specifically
"If a sub type overrides/implements a method originally defined in several parallel types of the hierarchy (e.g. two interfaces not extending each other, or a class and an interface not implemented by said class), no parameter constraints may be declared for that method at all nor parameters be marked for cascaded validation. This again is to avoid an unexpected strengthening of preconditions to be fulfilled by the caller."
allowParallelMethodsDefineParameterConstraints
in interface HibernateValidatorContext
allow
- flag determining whether validation will allow parameter constraints in parallel hierarchiesthis
following the chaining method patternpublic HibernateValidatorContext enableTraversableResolverResultCache(boolean enabled)
HibernateValidatorContext
TraversableResolver
results is enabled. The default
value is true
, i.e. the caching is enabled.
This behavior was initially introduced to cache the JPATraversableResolver
results but the map lookups it
introduces can be counterproductive when the TraversableResolver
calls are very fast.
enableTraversableResolverResultCache
in interface HibernateValidatorContext
enabled
- flag determining whether per validation call caching is enabled for TraversableResolver
results.this
following the chaining method patternpublic HibernateValidatorContext temporalValidationTolerance(Duration temporalValidationTolerance)
HibernateValidatorContext
temporalValidationTolerance
in interface HibernateValidatorContext
temporalValidationTolerance
- the tolerancethis
following the chaining method patternpublic HibernateValidatorContext constraintValidatorPayload(Object dynamicPayload)
HibernateValidatorContext
constraintValidatorPayload
in interface HibernateValidatorContext
dynamicPayload
- the payload passed to constraint validatorsthis
following the chaining method patternpublic Validator getValidator()
getValidator
in interface ValidatorContext
Copyright © 2007-2021 Red Hat, Inc. All Rights Reserved