bean-validation

Why am I getting an UnsupportedOperationException from Hibernate upon validation failure? I'm hoping for a ConstraintViolationException. Below is my DAO. When it passes validation it works fine. I'm using Hibernate and Hibernate Validator 4. I'm using Websphere 8.0. I think WebSphereExtendedJtaPlatform is the culprit, but I have no idea why. If I look at what's supposedly the source code for WebSphereExtendedJtaPlatform (follow link for the source) it looks like most of the methods there just throw UnsupportedOperationException. http://grepcode.com/file/repo1.maven.org/maven2/org.hibernate

I am trying to implement a crossfield validation (JSR-303) with a custom annotation on class level. However the isValid method is not called (but the initialize method). So my question is: Why is the isValid method not being called for this class level validator? Defining it on property level works! I tried it on JBoss AS 7 and Websphere AS 8. Here is the code and a JUnit test (which works) Test.java public class Test { @org.junit.Test public void test() throws ParseException { Person person = new Person(); SimpleDateFormat sdf = new SimpleDateFormat("yyyyMMDD"); person.setPartyClosingDateFrom

I have a test like below: public class TestSizeAnnotation { public static void main(String[] args) { System.out.println( Validation.buildDefaultValidatorFactory().getValidator().validate(new C())); } public static class P { private List<String> lst = newArrayList("AA"); @Size(max=0, message="P") public List<String> getLst() { return lst; } public void setLst(List<String> lst) { this.lst = lst; } } public static class C extends P { @Override @Size(max=5, message="C") public List<String> getLst() { return super.getLst(); } } } with the following output: [ConstraintViolationImpl

I am creating a website using Spring MVC and for persistence I am using Spring Data JPA with Hibernate 4 as my JPA provider. Validation is being handled at present with Hibernate Validator. I have a problem whereby my validators are being called twice and I can't figure out why. The main reason this is a problem is because the second time round, dependencies are not being autowired into the validator and I am getting a null pointer exception. The following is the sequence of calls leading up to the failure: The registration form is submitted and first the NotDefaultSectValidator is called and

I have to update information in my database. FacadePatient.java class code: public Patient update(Patient p) { Patient pat = em.find(Patient.class, p.getPatientId()); p.setPatientPhone(pat.getPatientPhone()); p.setPatientDateNaiss(pat.getPatientDateNaiss()); p.setPatientEmail(pat.getPatientEmail()); p.setPatientJob(pat.getPatientJob()); p.setPatientSmoking(pat.getPatientSmoking()); p.setPatientSize(pat.getPatientSize()); em.merge(pat); return p; } HV000030: No validator could be found for type: java.lang.Integer That will happen when you use JSR303 bean validation in flavor of Hibernate

model.... @Digits(integer=5, fraction=0, message="The value must be numeric and less than five digits") private int value; beans file.... <mvc:annotation-driven /> controller.... @RequestMapping(value = "/admin/save.htm", method = { RequestMethod.POST }) public ModelAndView saveSection(@Valid @ModelAttribute Section section, BindingResult result) { if(result.hasErrors()) { return new ModelAndView("admin/editSection", "section", section); } How do I restrict "value" to just numerics? If I enter something other than a number, I get this error: Failed to convert property value of type java.lang

Say I have the following simple java bean: class MyBean { private Date startDate; private Date endDate; //setter, getters etc... } Is there a mechanism in JSR 303 to create a custom validator that validates the constraint that startDate must be before endDate? It seems to me to be a common use case, yet I cannot find any examples of this kind of multiple property relationsship constraint. I can think of a few things to try. You could create a Constraint with a target of the type itself with an appropriate validator: @ValidateDateRange(start="startDate", end="endDate") public class MyBean { You