This means that enabling validation is really easy for common application scenarios, while at the same time still remaining very flexible for more advanced ones.I'm a noobie in Spring MVC To make Spring MVC 3 Validation fully work, Must it be that the Model Class (e.g. I'm sorry if this question is already answered in the Spring Docs or here in stackoverflow, it seems that I can't find the answer myself.While Data Annotations.aspx) approach is generally used for user input data validation, Fluent Validation that I’m going to introduce in this article might be better for delelopers with more benefits. Let's change this model using `Fluent Validation` ## User Input Data Validation with Fluent Validation You might need to download two packages from [Nu Get](https://nuget.org): library for our ASP. Instead of scattering those validation rules all over the places, we can place them into one spot so that we can get benefits, in terms of maintainablilty.Source code used in this post can be found at: Attribute classes like `Required`, `String Length` and `Compare` are responsible for data validation. Is Valid` value in the controller can be either `true` (valid) or `false` (invalid). One of downsides using is that it supports Web API with many limitations.
For adding Model just Right Click on Model inside that select Class.
As far as I'm concerned, a controller action should not be executed if Model State is invalid.
How is this type of request validation any different to decorating your action with a This works fine, most of the time.
If you are like me, [`Fluent Validation`](https://github.com/Jeremy Skinner/Fluent Validation) will be yours.
Of course, we can validate models through Web API with many walkarounds. According to the good news from the library creator/maintainer, Jeremy Skinner, he has been focusing on ASP.