I'm not 100% sure, but: do you need to call super.initBinder(request, binder)?
Fried Hoeben
2009-12-10 13:16:36
I'm not 100% sure, but: do you need to call super.initBinder(request, binder)?
It's quite a while back since I used Spring's validation framework. By looking at your code and the details you provided I didn't find any discrepancies. The only difference I noted when looking at my code was that I first created the CustomDateEditor, registered it with the binder and then called the super.initBinder.
Just for curiosity, did you try something like this
protected void initBinder(HttpServletRequest request, ServletRequestDataBinder binder) throws Exception {
binder.registerCustomEditor(Date.class, new CustomDateEditor(new SimpleDateFormat("yyyy-MM-dd"){{ setLenient(false);}},false));
super.initBinder(request, binder);
}
In the error it mentions 'java.sql.Date' - in both your custom property editory and you bean class is the Date class referred to java.sql.Date or java.util.Date?
I.e. have you imported the intended Date class in all places?