Re: locations of DST information --> debugging zoneinfo fix
Re: locations of DST information --> debugging zoneinfo fix
- Subject: Re: locations of DST information --> debugging zoneinfo fix
- From: "Mr. Pierre Frisch" <email@hidden>
- Date: Mon, 28 Jan 2008 22:48:33 -0800
Sorry for the noise.
On a typical machine there are 3 copies of the TimeZone info (and the
abbreviations). In the system, in the JVM and in the JavaFoundation.
The machine one is typically not used by Java applications. The Java
one is used if you use the Java Format and the JavaFoundation on is
used by NSTimeZone and NSTimestampFormatter as it uses NSTimeZone.
There may be some "interesting" effect if the JVM and NSTimeZone are
not in synch as NSTimestampFormatter uses a SimpleDateFormat
internaly but set the time zone using NSTimeZone. I have not tested
this case.
--
Pierre Frisch
email@hidden
On Jan 28, 2008, at 22:26, Lachlan Deck wrote:
Seeing as the thread has been hijacked by api squabbles (as
interesting as that is), just thought it'll be worth changing the
subject for my particular questions...
Just so it doesn't get lost amongst the noise :-)
Any ideas on the below?
Thanks.
On 29/01/2008, at 3:47 PM, Lachlan Deck wrote:
Alright, bringing this thread back to the problem at hand...
On 28/01/2008, at 6:06 PM, Lachlan Deck wrote:
On 28/01/2008, at 5:44 PM, Art Isbell wrote:
On Jan 27, 2008, at 8:10 PM, Lachlan Deck wrote:
What I meant was that I assumed that, as I'm seeing the correct
behaviour on my development machine with WO5.3, that I would
have thought that by embedding all system frameworks for 5.3 in
the app that the behaviour would continue to be correct on
deployment.
Seems like a valid assumption to me as far as the NSTimeZone is
concerned *if* none of the WO 5.4 frameworks containing time zone
info is being loaded (i.e., if the class paths exclude all WO 5.4
frameworks and jars). But if the JVM time zone info differs
between the dev and deployment machine, then Java TimeZone
calculations could differ.
Yeah, 5.4 is not in the picture at all, for the moment, whether in
dev or deploy.
Okay, the OS's (freebsd) has been updated to 2007k
- http://www.101tech.net/wordpress/2007/01/11/how-to-update-timezone-info-in-freebsd/
Java has also been updated:
- http://docs.info.apple.com/article.html?artnum=305129
For installed WO stuff, this has been updated:
/usr/local/Apple/Library/Frameworks/JavaFoundation.framework/
WebServerResources/Java/com/webobjects/foundation/TimeZoneInfo/
zoneinfo.zip
None of the WO5.2 installed jars have been updated -- as I assume
that these should not have any effect given that my app embed all
the system/local frameworks from my local dev machine which has a
recent enough zoneinfo snapshot.
However, WO's NSTimestampFormatter is not picking up the changes.
--> endDate:2008-03-31 09:00:00 Etc/GMT 'java formatted':2008-03-31
20:00 'nsformatted':2008-03-31 19:00
Is there something I missed?
with regards,
--
Lachlan Deck
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden