This is partly true only! JDBC offers methods: PreparedStatement.setDate(int, Date, Calendar) ResultSet.getDate(int, Calendar)
that can be used to control time zone conversions. I have done that when I used JDBC in the past. So the persistence layer clearly has the possibility to address this problem. I see this as a poor excuse for a programming error in org.hibernate.type.DateType and CalendarDateType. I am only observing entity beans (not the DB directly). I shouldn't need to care if the persistence uses JDBC, XML or does all in-memory. The persistence layer must hide such implementation details from the user. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3924192#3924192 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3924192 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
