incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Fang Wang <fang.w...@citrix.com>
Subject RE: [DISCUSS] Api refactoring -- validation
Date Thu, 13 Dec 2012 18:04:04 GMT
No silly questions at all. 
We are cleaning up the API input validation logic .  Goal is to clean up and do the access
check and validation logic at
API input as early as possible, not to scatter them into orchestration layer.

Thanks,
-Fang

-----Original Message-----
From: Chip Childers [mailto:chip.childers@sungard.com] 
Sent: Wednesday, December 12, 2012 9:31 PM
To: cloudstack-dev@incubator.apache.org
Subject: Re: [DISCUSS] Api refactoring -- validation

On Wed, Dec 12, 2012 at 6:16 PM, Fang Wang <fang.wang@citrix.com> wrote:
> Hi all,
>
> In our current API refactoring work, we plan to add a validation 
> annotation to Validate DB entity, validate some parameter range,  etc.
> We plan to add the @validate annotation to API commands.

This might be a silly question, but why the command classes and not the Dao's?  Is this to
validate the database inputs?  Or are we talking about cleaning up the API input validation
logic?

Thanks!

> IT is suggested we could use Hibernate Validator.  Anyone with 
> experience with Hibernate validator, how we could deploy it here?
>
> 1. is there a version we should definitely use?
> 2. Which option is better to integrate into our maven? Add it as dependency or as a plugin?
> 3. What is the latest version working with maven?
>
> Thanks for any input,
> -Fang
>
>

Mime
View raw message