[ http://opensource.atlassian.com/projects/hibernate/browse/HV-415?page=com... ] Hardy Ferentschik updated HV-415: --------------------------------- Component/s: engine -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/HV-415?page=com... ] Gunnar Morling commented on HV-415: ----------------------------------- Some more thoughts in this context: * Currently the classes related to method validation are located directly in org.hibernate.validator. I'm wondering whether we should create a new package "methodvalidation" and move this stuff there. According to it's JavaDoc the top-level package was intended for classes related to bootstrapping, and I think this makes pretty much sense. * Currently MethodValidator is an interface right on it's own. In especially one can't invoke any of Validator's methods such as validate() on a MethodValidator reference. So probably MethodValidator should extend Validator. But I'm also wondering whether we should have a dedicated interface for method validation or if we should provide a more general HV-specific extension of the Validator interface which might add also other functionalities to Validator (though I can't think of any right now). I'd prefer the latter approach, WDYT? -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/HV-415?page=com... ] Emmanuel Bernard commented on HV-415: ------------------------------------- about moving to a new package +1 methodvalidation might not be the best package name though. About extending Validator, I'm not sure. I think thanks to unwrap, we might not need it. I'd stay with a standalone interface for now and see how people react. -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/HV-415?page=com... ] Emmanuel Bernard commented on HV-415: ------------------------------------- My preference would be to use method Alternatives: interception //probably better if we add a real interception layer one day methodcheck methodinterception methodvalidation -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/HV-415?page=com... ] Hardy Ferentschik resolved HV-415. ---------------------------------- Resolution: Fixed Applied pull request. Not really sure what the issue would have been with {{methodvalidation}} as package name (maybe it is really a mouthful), but {{method}} works as well ;-) -- 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