That is good that you have a work around. I am still planning to look at this to see what has changed to cause the problem. Another option might be to use the @DateTimeFormat annotation or configure a global date format [1]. Support for a global date format was added in Spring 3.2 and I have a suspicion that this change might be a contributing factor.

From your log file, I assume that you have joda time on your classpath?

Phil Webb
added a comment - 03/Jan/13 10:53 AM Hi Srinivasa,
That is good that you have a work around. I am still planning to look at this to see what has changed to cause the problem. Another option might be to use the @DateTimeFormat annotation or configure a global date format [1] . Support for a global date format was added in Spring 3.2 and I have a suspicion that this change might be a contributing factor.
From your log file, I assume that you have joda time on your classpath?
[1] http://static.springsource.org/spring/docs/3.2.x/spring-framework-reference/html/validation.html#format-configuring-formatting-globaldatetimeformat

Srinivasa Attaluri
added a comment - 03/Jan/13 11:06 AM I do have JodaTime in the classpath. However, I am not using it in this context.
I do not want to use @DateTimeFormat as it it s attribute level annotation and that requires a lot of testing.
Tried using global configuration and had different issues. (May be I was missing something).
I stopped other options as I have a workaround that I could use in the BaseController.
As you mention, it would be helpful to get the bug fixed so it would be backward compatible.