No, the change above is just an optimization for a JDK 1.3 environment, in the case that commons-collections is available.Originally Posted by SuperMario
No, the change above is just an optimization for a JDK 1.3 environment, in the case that commons-collections is available.Originally Posted by SuperMario
Colin Sampaleanu
SpringSource - http://www.springsource.com
Is it possible to add a JIRA for this to not forget it?I am going to try to fix the Oracle date issues in queyForList though. We should be able to detect this Oracle class and do a getTimestamp instead. I'll post something when I have some code comitted - probably 1.1.2 release.
I have fixed this - it is now in CVS. This fix applies to queryForList and queryForObject. Oracle TIMESTAMP columns will now be returned as java.sql.Timestamp objects.
Cool, thanks.
I'm looking forward to the next release of SpringFramework.
Best Regards,
Mario