I thought that the timezone had nothing to do with Orion, too. But when I
run the same code in a standalone application (i.e. not loading the class
within Orion), I get a correct behaviour. And I'm using the same VM.
So, the standalone app yields a timezone w/ DST and a class within Orion
yields a TZ wo/ DST.
Weird. Any idea ?
regards,
Pierre
At 09:47 23.04.2002 +1000, you wrote:
ello,
Timezone is implemented as part of JDK, has nothing to do with the
application servers. I noticed that JDK1.3.0 had problems with timezone for
Sydney (Sydney had special daylight saving in year 2000 due to Olympic). But
JDK1.3.1 had fixed the problem.
cheers
romen
- Original Message -
From: Pierre Metrailler - shockfish / [EMAIL PROTECTED]
To: Orion-Interest [EMAIL PROTECTED]
Sent: Monday, April 22, 2002 8:02 PM
Subject: timezone issue
Hi all,
i've encountered a weird problem regarding timezones :
My system timezone is set to Europe/Zurich, GMT+2, since we are in DST.
Running a standalone java application and querying TimeZone.getDefault()
returns the correct timezone, i.e. the one with the correct ID
Europe/Zurich. The time is also correct.
Querying TimeZone.getDefault() within Orion yields a timezone with ID
Custom ! The offset is almost correct, excepted that it doesnt support
the daylight saving. (GMT+1). (TimeZone.getDefault()).useDaylightTime()
returns false, which is incorrect. Hence, the time is 1 hour late.
In short, Orion does not properly build the right timezone from the system
settings. Is there any way to address this problem ?
Regards,
Pierre
___
Pierre Metrailler, Software Engineer System Administrator
S h o c k f i s h Ltd, Event Communication Systems
PSE C - Parc Scientifique, CH-1015 Lausanne EPFL
Switzerland
public key http://shockfish.com/keys/pierre.asc
Enabling face-to-face communication.