• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag
 

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: NSTimestamp problem
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: NSTimestamp problem


  • Subject: Re: NSTimestamp problem
  • From: "Jerry W. Walker" <email@hidden>
  • Date: Wed, 10 Jan 2007 16:56:07 -0500

Heh, yes. It seems that between the various sovereign lawmakers around the world, the Sun Java library writers and the WO library writers, it's nearly impossible to write clear, clean time manipulation code.

I think this is the gods' way of keeping us from building time machines with our software. Remember the Tower of Babel! :-)

Jerry

On Jan 10, 2007, at 3:48 PM, Colin Curtin wrote:


This solution appears to cause problems with our apps. We get this in the WO app log when starting up:

ZoneInfo: wrong magic number: UTC
ZoneInfo: /System/Library/Frameworks/JavaVM.framework/Versions/ 1.5.0/Home/lib/zi/ZoneInfoMappings (No such file or directory)


Any ideas?

It appears to me that the zoneinfo files in /usr/share/ zoneinfo and those in the JavaVM framework have different magic numbers as the first error message indicates:


Yes, after looking through our logs, this is the case. After removing the 'zi' directory entirely, the VM reverted to using UTC. It seems our magic trick didn't do much of anything ;)

After finding this, I tried copying the java Phoenix zoneinfo file and replacing the java Los_Angeles one with it:

# cd /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/ Home/lib/zi/America
# sudo mv Los_Angeles Los_Angeles.old
# sudo cp Phoenix Los_Angeles


Phoenix doesn't switch to DST, so this seemed to fix it. I'm hesitant to use it - timestamps set now for mid-April might be an hour behind.

I hate time.

But since our data entry app only uses timestamps for checking date and not datetime, we should be okay.

I'll take a look at javazic and see how it does at compiling zoneinfo text files.

Whoopee,
Colin

--
Colin Curtin
Programmer, Kavli Institute for Theoretical Physics
UCSB
web:    http://www.kitp.ucsb.edu
email:  email@hidden
office: 805.893.6396

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40gmail.com


This email sent to email@hidden


--
__ Jerry W. Walker,
WebObjects Developer/Instructor for High Performance Industrial Strength Internet Enabled Systems


    email@hidden
    203 278-4085        office



_______________________________________________
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


References: 
 >Re: NSTimestamp problem (From: Colin Curtin <email@hidden>)
 >Re: NSTimestamp problem (From: Sacha Michel Mallais <email@hidden>)
 >Re: NSTimestamp problem (From: Art Isbell <email@hidden>)
 >Re: NSTimestamp problem (From: Colin Curtin <email@hidden>)

  • Prev by Date: Re: NSTimestamp problem
  • Next by Date: Exception: Deployment - FrontbasePlugIn - deadlock - WHY
  • Previous by thread: Re: NSTimestamp problem
  • Next by thread: Windows Development with WO 5.3
  • Index(es):
    • Date
    • Thread