Folks if there is no objection I would like to propose we adopt Hibernate Validator
Animesh -----Original Message----- From: Animesh Chaturvedi [mailto:[email protected]] Sent: Wednesday, November 14, 2012 2:29 PM To: [email protected] Subject: RE: [DISCUSS] API refactoring spec Prachi I was looking at the API refactoring document and had some comments on section 3.2.3 on validation. I think we can leverage Hibernate Validator instead of writing our own validators. It comes with decent collection of build in constraints and we can define new constraints with annotations and provide its implementation. Thanks Animesh -----Original Message----- From: Prachi Damle [mailto:[email protected]] Sent: Wednesday, November 14, 2012 10:51 AM To: [email protected] Subject: [DISCUSS] API refactoring spec I have put some ideas together, regarding refactoring the current API commands to support better documentation generation, parameter validation and some code cleanup needed for future acl work. Please take a look and let me know any suggestions/comments on the proposal: https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+API+refactoring Thanks, Prachi -----Original Message----- From: Prachi Damle [mailto:[email protected]] Sent: Tuesday, November 13, 2012 1:10 PM To: [email protected] Subject: RE: Git Push Summary David, This involves some annotation work for existing API commands to facilitate generation of documentation, better packaging, parameter validation at API layer and also the access control checks at API layer. I am putting together these ideas in a spec and will share it with the list for discussion. Thanks, Prachi -----Original Message----- From: David Nalley [mailto:[email protected]] Sent: Tuesday, November 13, 2012 11:52 AM To: [email protected] Subject: Re: Git Push Summary Sounds fascinating API refactoring?? In what way? On Tue, Nov 13, 2012 at 2:49 PM, <[email protected]> wrote: > Updated Branches: > refs/heads/api_refactoring [created] 70a5a2232
