[hibernate-issues] [Hibernate-JIRA] Commented: (HV-274) Write a programmatic mapping API for constraint declarations

Emmanuel Bernard (JIRA) noreply at atlassian.com
Wed May 12 08:37:25 EDT 2010


    [ http://opensource.atlassian.com/projects/hibernate/browse/HV-274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=37080#action_37080 ] 

Emmanuel Bernard commented on HV-274:
-------------------------------------

{quote}
The idea I had was not to allow the interchanging. You are loosing no functionality when enforcing first message, then message, payload and finally elements. In fact the constraint definitions become more consistent. Concrete means that, that only the first level would have a "with".
{quote}

What bothers me in this model is that I am forced to either:
- define a message even when I want the default
- or if you have multiple with, you have to know the API designer's choice on putting message before payload otherwise the methods disappear in my list of available methods as soon as I make a choice too far (ie withPayload().andMess[] never autocompletes and frustrate the API user).

> Write a programmatic mapping API for constraint declarations
> ------------------------------------------------------------
>
>                 Key: HV-274
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-274
>             Project: Hibernate Validator
>          Issue Type: New Feature
>          Components: engine
>    Affects Versions: 4.0.2.GA
>            Reporter: Emmanuel Bernard
>            Assignee: Hardy Ferentschik
>             Fix For: 4.1.0
>
>


-- 
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

        


More information about the hibernate-issues mailing list