public interface HibernateConstraintViolationBuilder extends ConstraintValidatorContext.ConstraintViolationBuilder
ConstraintValidatorContext.ConstraintViolationBuilder.ContainerElementNodeBuilderCustomizableContext, ConstraintValidatorContext.ConstraintViolationBuilder.ContainerElementNodeBuilderDefinedContext, ConstraintValidatorContext.ConstraintViolationBuilder.ContainerElementNodeContextBuilder, ConstraintValidatorContext.ConstraintViolationBuilder.LeafNodeBuilderCustomizableContext, ConstraintValidatorContext.ConstraintViolationBuilder.LeafNodeBuilderDefinedContext, ConstraintValidatorContext.ConstraintViolationBuilder.LeafNodeContextBuilder, ConstraintValidatorContext.ConstraintViolationBuilder.NodeBuilderCustomizableContext, ConstraintValidatorContext.ConstraintViolationBuilder.NodeBuilderDefinedContext, ConstraintValidatorContext.ConstraintViolationBuilder.NodeContextBuilder
Modifier and Type | Method and Description |
---|---|
default HibernateConstraintViolationBuilder |
enableExpressionLanguage()
Enable Expression Language with the default Expression Language feature level for the constraint violation
created by this builder if the chosen
MessageInterpolator supports it. |
HibernateConstraintViolationBuilder |
enableExpressionLanguage(ExpressionLanguageFeatureLevel level)
Enable Expression Language for the constraint violation created by this builder if the chosen
MessageInterpolator supports it. |
addBeanNode, addConstraintViolation, addContainerElementNode, addNode, addParameterNode, addPropertyNode
@Incubating default HibernateConstraintViolationBuilder enableExpressionLanguage()
MessageInterpolator
supports it.
If you enable this, you need to make sure your message template does not contain any unescaped user input (such as
the validated value): use addExpressionVariable()
to inject properly escaped variables into the template.
@Incubating HibernateConstraintViolationBuilder enableExpressionLanguage(ExpressionLanguageFeatureLevel level)
MessageInterpolator
supports it.
If you enable this, you need to make sure your message template does not contain any unescaped user input (such as
the validated value): use addExpressionVariable()
to inject properly escaped variables into the template.
level
- The Expression Language features level supported.Copyright © 2007-2021 Red Hat, Inc. All Rights Reserved