The latest version of the update content of Hibernate Validator Engine RELOCATION Artifact in the latest version of
The latest version of Hibernate Validator Engine Relocation Artifact update content
Hibernate Validator is one of the most popular verification frameworks in the Java field to perform data verification in applications.The Hibernate Validator engine regulating component is one of the new features introduced in its latest version.In this article, we will explore the purpose of this new feature and how to use it.
First, let's learn about the role of the Hibernate Validator engine.When we use Hibernate Validator in an application, we usually need to add dependencies in the project to introduce related class libraries.Some problems may be encountered in the process of introducing libraries, such as conflict or name conflict.To solve these problems, Hibernate Validator introduced engine regulating components.
The role of the engine regulating component is to reinterpret the class library (including related dependencies) of the Hibernate Validator engine to a new package name to avoid conflicting with other types of libraries.In this way, we can safely use the Hibernate Validator in the project without having to worry about the problem of conflict or class library version of conflict.
Specifically, the Hibernate Validator engine regulating component provides a new component coordinate that can be cited directly in the project construction file.Below is an example of using Maven to build tools:
<dependency>
<groupId>org.hibernate.validator</groupId>
<artifactId>hibernate-validator-engine-relocation</artifactId>
<Version> Latest Version Number </Version>
</dependency>
By adding this dependencies in the project construction document, we can directly use the Hibernate Validator engine without having to care about the problem of the package name or version conflict of the class library.
Except for the change of the method of rewriting components, the Hibernate Validator engine regulating component itself does not have many changes in itself.It is just to provide more convenient ways to use and solve some common library conflicts.
When using the Hibernate Validator engine regattting components, we can use its API as usual as usual for data verification.The following is a simple sample code:
import javax.validation.Validation;
import javax.validation.Validator;
import javax.validation.ValidatorFactory;
public class Main {
public static void main(String[] args) {
ValidatorFactory factory = Validation.buildDefaultValidatorFactory();
Validator validator = factory.getValidator();
// Check the data
Person person = new Person();
Set<ConstraintViolation<Person>> violations = validator.validate(person);
for (ConstraintViolation<Person> violation : violations) {
System.out.println(violation.getMessage());
}
}
public static class Person {
@Notnull (Message = "Name cannot be empty")
private String name;
// omit other attributes and methods ...
}
}
In the above example, we use the API of Hibernate Validator to check the attributes of the Person object.If the attribute value does not meet the relevant constraints, the verification results will be placed in the Violations set and the corresponding error information will be output.
To sum up, the Hibernate Validator engine regattting component is a new feature in the latest version of Hibernate Validator. It is used to easily use the Hibernate Validator engine in the project and avoid the problem of library conflict.It does not have much functional change, just provides a more convenient way to use.By introducing the dependence of engine regulating components, we can use the Hibernate Validator API as usual as usual for data verification.
