1. Persist an entity with a Date property 2. Change the time zone of the JBoss server (or call TimeZone.setDefault) 3. Read the entity from the persistence layer
Now the Date property has a different value than before! This is extremely bad. Date objects are semantically not specific to a time zone and they store their internal state as milliseconds in GMT. This behaviour can lead to numerous problems: * Automatic system time zone changes between summer (daylightsavings) and winter time * Two JBoss instances in different time zones sharing a common database * Moving systems between time zones * Manually messing with a system's timezone configuration I would like to know how this timezone modality of the persistence layer can be addressed. I yet have to try out what happens when you change the TZ of the DB server... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3923980#3923980 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3923980 ------------------------------------------------------- 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
