Hello,
Boris Kovalenko wrote:
Hello!
...
Ok, this helps... now local dates are ok. Thank You, Volker! But now I
have problems with dates I reading from SQL. What should I do with them?
Is there best practices how to work with dates?
Is that only for old values or also for the new ones
Volker Weber wrote:
Hello!
if only for the old ones it seems that your old dates in the database
are not GMT based.
Ok, I will check and read DB docs more carefull. No problems, as I still
use test DB so I can convert and test anything.
Hmmm... when I directly use Asia/Yekaterinburg
Hello!
Hmm... but TimeZone.getDefault() returns type of TimeZone, not the Date!
your right, it must be
public TimeZone getTimeZone() { return TimeZone.getDefault();}
but this is the object type as expected by the timeZones valueExpression
in the converter.
Ok, this helps... now local dates
Volker Weber wrote:
Hello!
you can implement it like this
public Date getTimeZone() { return TimeZone.getDefault();}
Hmm... but TimeZone.getDefault() returns type of TimeZone, not the Date!
Asia/Yekaterinburg is recognized by my java implementation,
Hmm... I use 1.4.2_04, will
4 matches
Mail list logo