The differences are not extensive, but do exist. I believe its mostly in the US where an airport is near a state/zone boundary.
You will need to work to create a new subclass of DateTimeZone, with the associated provider factories. I would obviously recommend that you download a source version of joda-time to start from. FixedDateTimeZone is a good simple zone class to start from.
Stephen
On 02/06/06, vijay konnackal <[EMAIL PROTECTED]> wrote:
I have a requirement to drive the joda TimeZone from the timezone data
provided by IATA - I work in the Travel industry and the hosts seems
to use the IATA data for timezones.
The IATA data is not as feature rich as OlsonDB. IATA does not have
data prior to 1999 and does not have recurring rules as in OlsonDB. I
am thinking of somehow using the OlsonDb for filling the missing years
- past and future. Has anyone done this before? Any pointers to how to
achieve this will be very useful to me.
Also does anyone know if the OlsonDB and IATA data differs a lot.
We need zero downtime during config updates (including tz data
update), which would warrant a different TimeZoneProvider
implementation that is capable of reloading the data. This was one of
the many many reasons for choosing Joda over jdk Calendar/Date.
-vijay
_______________________________________________
Joda-interest mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/joda-interest
_______________________________________________ Joda-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/joda-interest
