StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
12149331
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
8
CommunityOwnedDate
2012-10-01T19:41:20.077
CreationDate
2012-08-27T20:42:26.397
FavoriteCount
0
LastActivityDate
2016-09-23T00:45:55.293
LastEditDate
2017-05-23T12:18:20.913
LastEditorUserId
-1
OwnerUserId
400545
ParentId
12146298
PostTypeId
2
Score
297
ViewCount
0
LastEditorDisplayName
text
Body
With Spring MVC, there are 3 different ways to perform validation : using annotation, manually, or a mix of both. There is not a unique "cleanest and best way" to validate, but there is probably one that fits your project/problem/context better. Let's have a User : <pre><code>public class User { private String name; ... } </code></pre> Method 1 : If you have Spring 3.x+ and simple validation to do, use <code>javax.validation.constraints</code> annotations (also known as JSR-303 annotations). <pre><code>public class User { @NotNull private String name; ... } </code></pre> You will need a JSR-303 provider in your libraries, like <a href="http://www.hibernate.org/subprojects/validator.html" rel="noreferrer">Hibernate Validator</a> who is the reference implementation (this library has nothing to do with databases and relational mapping, it just does validation :-). Then in your controller you would have something like : <pre><code>@RequestMapping(value="/user", method=RequestMethod.POST) public createUser(Model model, @Valid @ModelAttribute("user") User user, BindingResult result){ if (result.hasErrors()){ // do something } else { // do something else } } </code></pre> Notice the @Valid : if the user happens to have a null name, result.hasErrors() will be true. Method 2 : If you have complex validation (like big business validation logic, conditional validation across multiple fields, etc.), or for some reason you cannot use method 1, use manual validation. It is a good practice to separate the controller’s code from the validation logic. Don't create your validation class(es) from scratch, Spring provides a handy <code>org.springframework.validation.Validator</code> interface (since Spring 2). So let's say you have <pre><code>public class User { private String name; private Integer birthYear; private User responsibleUser; ... } </code></pre> and you want to do some "complex" validation like : if the user's age is under 18, responsibleUser must not be null and responsibleUser's age must be over 21. You will do something like this <pre><code>public class UserValidator implements Validator { @Override public boolean supports(Class clazz) { return User.class.equals(clazz); } @Override public void validate(Object target, Errors errors) { User user = (User) target; if(user.getName() == null) { errors.rejectValue("name", "your_error_code"); } // do "complex" validation here } } </code></pre> Then in your controller you would have : <pre><code>@RequestMapping(value="/user", method=RequestMethod.POST) public createUser(Model model, @ModelAttribute("user") User user, BindingResult result){ UserValidator userValidator = new UserValidator(); userValidator.validate(user, result); if (result.hasErrors()){ // do something } else { // do something else } } </code></pre> If there are validation errors, result.hasErrors() will be true. Note : You can also set the validator in a @InitBinder method of the controller, with "binder.setValidator(...)" (in which case a mix use of method 1 and 2 would not be possible, because you replace the default validator). Or you could instantiate it in the default constructor of the controller. Or have a @Component/@Service UserValidator that you inject (@Autowired) in your controller : very useful, because most validators are singletons + unit test mocking becomes easier + your validator could call other Spring components. Method 3 : Why not using a combination of both methods? Validate the simple stuff, like the "name" attribute, with annotations (it is quick to do, concise and more readable). Keep the heavy validations for validators (when it would take hours to code custom complex validation annotations, or just when it is not possible to use annotations). I did this on a former project, it worked like a charm, quick & easy. Warning : you must not mistake validation handling for exception handling. <a href="https://stackoverflow.com/a/12661291/400545">Read this post</a> to know when to use them. References : <ul> <li><a href="http://web.archive.org/web/20120508030459/http://blog.orange11.nl/2009/08/04/bean-validation-integrating-jsr-303-with-spring" rel="noreferrer">A very interesting blog post about bean validation</a> (<a href="http://blog.orange11.nl/2009/08/04/bean-validation-integrating-jsr-303-with-spring/" rel="noreferrer">Original link</a> is dead)</li> <li><a href="http://alasdoo.com/2011/07/data-validation-conversion-basics-custom-error-messages-in-spring-mvc" rel="noreferrer">Another good blog post about validation</a></li> <li><a href="http://static.springsource.org/spring/docs/current/spring-framework-reference/html/validation.html" rel="noreferrer">Latest Spring documentation about validation</a></li> </ul>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POSpring MVC: How to perform validation?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USCommunity
UserOwnerUserId
1. USJerome Dalbert
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POSpring MVC: How to perform validation?
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.