Hibernate Validator is community driven and as such the roadmap constantly evolves to reflect the users needs and contributions.
You can find a fine grained roadmap in our issue tracker, but this page is a good starting point to see where we are going.
Hibernate Validator 9.0
For a full list of issues currently planned for this series, see here.
-
HV-1991 Upgrade to JDK 17 as the baseline and drop JDK 11 compatibility
-
HV-1979 Upgrade to jakarta.validation-api 3.1.0
-
HV-1975 Remove the Security Manager integration. With Security Manager being deprecated for some time and planned for removal, its integration in Hibernate Validator becomes obsolete.
-
HV-1967 Remove the obsolete Wildfly patching module
hibernate-validator-modules
or consider replacing it with the feature pack. -
Make Hibernate Validator build reproducible.
-
Include more constraints.
Future versions
- Engine
-
Improve performance for cascading validation of large lists. (HV-1831) Explore the ability to validate an object and a list of changes (BVAL-214)
Explore support for constraint ordering (BVAL-248)
Explore the usage of Jandex (a Java annotation indexer and offline reflection library) to build the metadata (HV-644)
Explore message interpolators receiving several locales (HV-1436) Explore taking some distance from the reflection API (e.g. dealing withType
is rather confusing, replace some of the types with memory-friendly counterparts (Method
?), do not rely onTypeVariable
). Note that it might also help with the future usage of Jandex for annotation discovery.
Add support for JSON validation at the root level (i.e. validating a root JSON object) and at the property level (i.e. validating a JSON property of a given bean) - Java modularization
-
Providing Hibernate Validator with JDK 9 module descriptors Explore usage of ResourceBundleProvider for obtaining validation error messages from other modules
Optionally support usage of method handles for accessing bean states (HV-1226) - Remote API
-
Provide an HTTP endpoint which allows to validate single properties and also exposes constraint metadata via JSON (HV-1500). Web applications can integrate that endpoint to allow client-side validation of their models.
- Annotation processor improvements
-
Taking into account new places where constraint annotations can be placed (HV-879)
Taking into account XML configuration (HV-308)