I've had this problem 2 or 3 times now using Castor JDO 0.9.x and it's extremely annoying. In fact, in my case, it only seems to happen on the production web server. I cannot duplicate it on the development web server pointing at either the development or the production databases. So, the only way I can test it is IN PRODUCTION!!! Argh.
I've found the recommended solution in the JDO mailing list archives again. Apparently this exception can happen with fields of type float, double, or date. In these cases, the recommended fix is to change the mapping file to tell JDO to ignore the dirty check on those fields. Here's an example:
<sql name="foo" type="date" dirty="ignore" />
8:30:15 AM 
|
