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

[ http://opensource.atlassian.com/projects/hibernate/browse/HV-442?page=com... ] Gunnar Morling updated HV-442: ------------------------------ Description: 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. In order to avoid irritations we should make clear in the documentation (http://docs.jboss.org/hibernate/validator/4.1/reference/en-US/html/valida...) 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): {quote} 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. {quote} 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 issue is based on a post in the HV forum (https://forum.hibernate.org/viewtopic.php?f=9&t=1009701). was: 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. In order to avoid irritations we should make clear in the documentation (http://docs.jboss.org/hibernate/validator/4.1/reference/en-US/html/valida...) 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): {quote} 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. {quote} 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). Issue Type: Improvement (was: Bug) Summary: Make clear in the documentation which types are supported for built-in constraints (was: Make clear in the documentation, which types are supported for built-in constraints) -- 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.... - For more information on JIRA, see: http://www.atlassian.com/software/jira