|
| 1 | +// SPDX-License-Identifier: Apache-2.0 |
| 2 | +// Copyright Red Hat Inc. and Hibernate Authors |
| 3 | += Hibernate Validator {hvVersion} - Jakarta Validation Reference Implementation: Migration Guide from {hvVersionPreviousShort} |
| 4 | +:doctype: book |
| 5 | +:revdate: {docdate} |
| 6 | +:sectanchors: |
| 7 | +:xrefstyle: full |
| 8 | +:anchor: |
| 9 | +:toc: left |
| 10 | +:toclevels: 4 |
| 11 | +:sectnumlevels: 5 |
| 12 | +:docinfodir: {docinfodir} |
| 13 | +:docinfo: shared,private |
| 14 | +:title-logo-image: image:hibernate_logo_a.png[align=left,pdfwidth=33%] |
| 15 | +:html-meta-description: Hibernate Validator, Annotation based constraints for your domain model - Migration Documentation |
| 16 | +:html-meta-keywords: hibernate, validator, hibernate validator, validation, jakarta bean validation, jakarta validation, bean validation |
| 17 | +:html-meta-canonical-link: https://docs.jboss.org/hibernate/stable/validator/migration/en-US/html_single/ |
| 18 | +:html-meta-version-family: {hvVersionShort} |
| 19 | +:version-selector-enabled: true |
| 20 | + |
| 21 | +[[introduction]] |
| 22 | +== [[_introduction]] Introduction |
| 23 | + |
| 24 | +The aim of this guide is to assist you migrating an existing application using any version `{hvVersionPreviousShort}.x` |
| 25 | +of Hibernate Validator to the latest of the `{hvVersionShort}.x` series. |
| 26 | + |
| 27 | +NOTE: If you think something is missing or something does not work, please link:https://hibernate.org/community[contact us]. |
| 28 | + |
| 29 | +If you're looking to migrate from an earlier version, you should migrate step-by-step, from one minor version to the next, |
| 30 | +following the migration guide of link:https://hibernate.org/validator/documentation/migrate/[each version]. |
| 31 | + |
| 32 | +[WARNING] |
| 33 | +==== |
| 34 | +As this release includes significant changes to the processed bean tracking, path implementation and related areas, |
| 35 | +we encourage users to give it a try and report any findings, especially if there are non-trivial validation scenarios. |
| 36 | +==== |
| 37 | + |
| 38 | +[[requirements]] |
| 39 | +== Requirements |
| 40 | + |
| 41 | +The requirements of Hibernate Validator {hvVersionShort} |
| 42 | +are the same as those of Hibernate Validator {hvVersionPreviousShort}. |
| 43 | + |
| 44 | +[[artifact-changes]] |
| 45 | +== Artifacts |
| 46 | + |
| 47 | +The coordinates of Maven artifacts in Hibernate Validator {hvVersionShort} |
| 48 | +are the same as in Hibernate Validator {hvVersionPreviousShort}. |
| 49 | + |
| 50 | +[[configuration]] |
| 51 | +== Configuration |
| 52 | + |
| 53 | +The configuration properties in Hibernate Validator {hvVersionShort}, |
| 54 | +in general, are backward-compatible with Hibernate Validator {hvVersionPreviousShort}. |
| 55 | + |
| 56 | +[[api]] |
| 57 | +== API |
| 58 | + |
| 59 | +The https://hibernate.org/community/compatibility-policy/#code-categorization[API] |
| 60 | +in Hibernate Validator {hvVersionShort} |
| 61 | +is, in general, backward-compatible with Hibernate Validator {hvVersionPreviousShort}. |
| 62 | + |
| 63 | +[[spi]] |
| 64 | +== SPI |
| 65 | + |
| 66 | +The https://hibernate.org/community/compatibility-policy/#code-categorization[SPI] |
| 67 | +in Hibernate Validator {hvVersionShort} |
| 68 | +is, in general, backward-compatible with Hibernate Validator {hvVersionPreviousShort}. |
| 69 | + |
| 70 | +[[behavior]] |
| 71 | +== Behavior |
| 72 | + |
| 73 | +The behavior of Hibernate Validator {hvVersionShort} |
| 74 | +is, in general, backward-compatible with Hibernate Validator {hvVersionPreviousShort}. |
| 75 | + |
| 76 | +Keep in mind that the internal representation of the `Path` and `Node` became mutable during validation process, |
| 77 | +so do not rely on these being immutable in your traversable resolvers. |
| 78 | +The `Path` and `Node` representations within the `ConstraintViolation` remains immutable. |
| 79 | + |
0 commit comments