[hibernate-issues] [Hibernate-JIRA] Created: (HV-442) Make clear in the documentation, which types are supported for built-in constraints

[Gunnar Morling (JIRA)]

Make clear in the documentation, which types are supported for built-in constraints
-----------------------------------------------------------------------------------

                 Key: HV-442
                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-442
             Project: Hibernate Validator
          Issue Type: Bug
          Components: documentation
    Affects Versions: 4.1.0.Final
            Reporter: Gunnar Morling
             Fix For: 4.2.0.CR1


Hibernate Validator supports the standard constraints defined in the Bean Validation AP at more types than required by the specification. E.g. @Min/@Max are supported for Strings, which is beyond what's defined in the spec.

We should make clear in the documentation (http://docs.jboss.org/hibernate/validator/4.1/reference/en-US/html/validator-usingvalidator.html#validator-defineconstraints-builtin) which types are supported by HV in addition to the BV specification (for @Past/@Future we already do describe this for the Joda types for example).

Furthermore the annotation processor documentation says (reference guide and web site):

> Have you ever caught yourself by unintentionally doing things like
> annotating Strings with @Min to specify a minimum length (instead of using @Size)
> ...?
> Then the Hibernate Validator Annotation Processor is the right thing for you.

This example is misleading, as the AP won't mark this situation as an erronous (the described misunderstanding, that @Min would refer to the String length can still happen, though).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira