I have Spring MVC with JDBC that uses @Valid annotations, and all this works very well, including validation.
Now I have created a similar webapp that uses Hibernate (instead of JDBC), and it also works well so far.
I decided to βpinβ the check before continuing with a large number of domains, etc.
So, I added @Valid to the save process in the controller as follows:
@RequestMapping(value = "/productgroup/save", method = RequestMethod.POST)
public String updateProductGroup(**@Valid** ProductGroup productGroup, BindingResult bindingResult)
This is the only change I am making and now it is crashing:
SEVERE: Servlet.service () for servlet appServlet threw exception
java.lang.NoSuchMethodError: javax.persistence.Persistence.getPersistenceUtil () Ljavax / persistence / PersistenceUtil;
at org.hibernate.validator.engine.resolver.JPATraversableResolver.isReachable (JPATraversableResolver.java:33)
at org.hibernate.validator.engine.resolver.DefaultTraversableResolver.isReachable (DefaultTraversableResolver.java:112)
at org.hibernate.validator.engine.resolver.SingleThreadCachedTraversableResolver.isReachable (SingleThreadCachedTraversableResolver.java:47)
at org.hibernate.validator.engine.ValidatorImpl.isValidationRequired (ValidatorImpl.java:764)
at org.hibernate.validator.engine.ValidatorImpl.validateConstraint (ValidatorImpl.javahaps31)
at org.hibernate.validator.engine.ValidatorImpl.validateConstraintsForRedefinedDefaultGroup (ValidatorImpl.java:278)
at org.hibernate.validator.engine.ValidatorImpl.validateConstraintsForCurrentGroup (ValidatorImpl.java:260)
at org.hibernate.validator.engine.ValidatorImpl.validateInContext (ValidatorImpl.java:213)
at org.hibernate.validator.engine.ValidatorImpl.validate (ValidatorImpl.java:119)
at org.springframework.validation.beanvalidation.SpringValidatorAdapter.validate (SpringValidatorAdapter.java:86)I use: org.hibernate Overwinter-validator 4.0.2.GA clear javax.validation validation-api 1.0.0.GA
I tried @NotEmpty both in the ProductGroup productGroupName field and in my Getter.
Any ideas?
I really never expected any problems here, since I had no problems getting validation to work in my version of JDBC ...
source
share