Darren Marsh wrote:I'm in Australia. This application was originally written for 1.4 and hasn't had any problems or need any java fixes to make it work. Only Java 6 has this problem.
Well that's suspicious right there - Australia changed their rules twice since JDK 1.4 came out, no? I suspect that your tests are not as comprehensive as they might be. Could be you're just now noticing a problem that's been around for a while. Where in Australia are you? Saying "Coordinated Universal Time" seems bogus, since UTC doesn't have daylight savings at all.
Charlie wrote:It's not Java. It's Windows bizarre handling of time and DST.
Well, I'm all for blaming Windows in most cases. But here, I'm more inclined to blame the very concept of DST. It's inherently evil. It would be bad enough if it followed consistent rules from country to country, and from year to year. But it doesn't. It's something that any random country (USA, Australia) can change on a whim.
On the plus side, this creates some work for us programmers. Huzzah! Except, well, I have enough work already, thanks. Any rules that exist solely to make things more complicated need to be jettisoned, IMO.
Yeah, I know the chance of changing this is minimal (at the moment). But hey, you raised the blame issue - I just want the finger pointed squarely at the true culprit.