The current Solaris-to-Java time zone mapping ignores DST rules for the numerical mapping and may pick up a wrong time zone that has different DST rules if the TZ value is set to define time zone rules (rather than a zone ID).
For example, TZ=XST7XDT8,0/0:00,0/1:00 is mapped to America/Denver which has the different DST schedule. (This TZ value is used in a regression test and this wrong result is taken as a correct behavior.)
The TZ value has to be parsed and generate parameters for TimeZone construction.
Need to dynamically register time zone abbreviations in a TimeZone object.
At least the wrong mapping must be fixed.