Skip to content

Commit

Permalink
Update links to Hibernate Validator 5.3.x documentation
Browse files Browse the repository at this point in the history
Closes dropwizard#2137

(cherry picked from commit ab1b95b)
  • Loading branch information
joschi committed Sep 8, 2017
1 parent d8a4043 commit 350ff22
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions docs/source/manual/validation.rst
Expand Up @@ -76,9 +76,9 @@ detailing the validation errors: ``name may not be empty``
class must be marked ``@Valid``. For more information, see the Hibernate Validator documentation
on `Object graphs`_ and `Cascaded validation`_.

.. _Object graphs: http://docs.jboss.org/hibernate/validator/5.2/reference/en-US/html/chapter-bean-constraints.html#section-object-graph-validation
.. _Object graphs: https://docs.jboss.org/hibernate/validator/5.3/reference/en-US/html_single/#section-object-graph-validation

.. _Cascaded validation: http://docs.jboss.org/hibernate/validator/5.2/reference/en-US/html/chapter-method-constraints.html#_cascaded_validation
.. _Cascaded validation: https://docs.jboss.org/hibernate/validator/5.3/reference/en-US/html_single/#example-cascaded-validation

Since our entity is also annotated with ``@NotNull``, Dropwizard will also guard against ``null``
input with a response stating that the body must not be null.
Expand Down Expand Up @@ -275,7 +275,7 @@ Annotations
In addition to the `annotations defined in Hibernate Validator`_, Dropwizard contains another set of annotations,
which are briefly shown below.

.. _annotations defined in Hibernate Validator: http://docs.jboss.org/hibernate/validator/5.2/reference/en-US/html/chapter-bean-constraints.html#section-builtin-constraints
.. _annotations defined in Hibernate Validator: https://docs.jboss.org/hibernate/validator/5.3/reference/en-US/html_single/#section-builtin-constraints

.. code-block:: java
Expand Down Expand Up @@ -331,7 +331,7 @@ The ``@Validated`` annotation allows for `validation groups`_ to be specifically
default group. This is useful when different endpoints share the same entity but may have different
requirements.

.. _validation groups: https://docs.jboss.org/hibernate/validator/5.2/reference/en-US/html/chapter-groups.html
.. _validation groups: https://docs.jboss.org/hibernate/validator/5.3/reference/en-US/html_single/#chapter-groups

Going back to our favorite ``Person`` class. Let's say we initially coded it such that ``name`` has
to be non-empty, but realized that business requirements needs the max length to be no more than 5.
Expand Down

0 comments on commit 350ff22

Please sign in to comment.