Determine an order for the constraint mapping fluent API
--------------------------------------------------------
Key: HV-485
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HV-485
Project: Hibernate Validator
Issue Type: Improvement
Reporter: Gunnar Morling
Fix For: 4.2.0.CR1
Currently constraints can be defined in any order using the programmatic API, e.g. type
-> parameter -> property -> return value. The suggested order is type ->
property -> parameter -> return value.
This should easily be implemented by splitting {{TypeTargets}} into separate interfaces
and deriving each creational context interface from the required target interface(s).
--
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