Hey guys,
I just solved the issue. The problem is another application that is deployed in the same server and has this code inside a Servlet
@Override
public void init() throws ServletException {
TimeZone.setDefault(new SimpleTimeZone(TimeZone.getDefault().getRawOffset(), "America/Sao_Paulo", Calendar.OCTOBER, 05, 0, 3600000 * 1 + 60000 * 0, Calendar.FEBRUARY, 25,
0, 3600000 * 1 + 60000 * 0, 3600000));
super.init();
}
Btw, I still want to understand why a context reload also make it work right.
Thanks :-)
On Fri, Sep 18, 2009 at 12:57 AM, Diego Plentz
<diego.pires@...> wrote:
Hey guys,
What exactly a context reload does? Context: I start jetty right now, it starts ok and I enter my application. _All_ times are displayed with hour+1. In the DB(postgresql,btw) the rows are right. BUT, if I do a reload in the application context, suddenly, everything became right: timestamps with hour are displayed right. I know it is the reload that is doing it, because I have more then one war in the same server, and I must reload all contexts to all applications runs as we wish (yes, if I reload just one application, just THAT application behave as it must behave). ANY thoughts?
--
http://plentz.org
