You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Change any kiwi custom validators that currently use EL so they do not require its use. This is due to a change in Hibernate Validator 6.2.x in which the expression language is disabled by default for custom validators. Refer to #690 for a more thorough discussion. By removing the requirement for using EL in our validators, we can safely upgrade to Hibernate Validator 6.2.x.
The text was updated successfully, but these errors were encountered:
Remove use of EL in Range and FieldRangeValidator by splitting each
message template into separate templates, one that uses the min/max
annotation value and one that uses the minLabel/maxLabel annotation
value. This makes the validator implementation a little more
complicated, by requiring them to determine which template to use.
This is done once in the initialize method.
See #690 for details on Hibernate Validator disabling EL by default
in version 6.2.x and higher.
Closes#721
Remove use of EL in Range and FieldRangeValidator by splitting each
message template into separate templates, one that uses the min/max
annotation value and one that uses the minLabel/maxLabel annotation
value. This makes the validator implementation a little more
complicated, by requiring them to determine which template to use.
This is done once in the initialize method.
See #690 for details on Hibernate Validator disabling EL by default
in version 6.2.x and higher.
Closes#721
Change any kiwi custom validators that currently use EL so they do not require its use. This is due to a change in Hibernate Validator 6.2.x in which the expression language is disabled by default for custom validators. Refer to #690 for a more thorough discussion. By removing the requirement for using EL in our validators, we can safely upgrade to Hibernate Validator 6.2.x.
The text was updated successfully, but these errors were encountered: