Timezones are not handled correclty in all cases in the Query interface

Most Elasticfox users also affected:

Elasticfox version 1.6.000107, with [about:config] setting [ec2ui.debugging.enabled = true] shows the following timestamping on the debug console:

[ec2ui] QueryParams [Action=DescribeInstances&AWSAccessKeyId=ISMvKXpXpadDiUoOSoAfww&SignatureVersion=1&Timestamp=2009-08-12T12%3A22%3A27Z&Version=2009-03-01&Signature=VhFTyn3A8KBrD5h9mzfKzVYoEmc%3D]

Note the Timestamp: 2009-08-12T12:22:27Z that was added to the request:

This is the correct current UTC time, so Elasticfox always converts to UTC (Z), my Eucalyptus machine is running in CEST, thus I run in exactly the same problem, and.... it likely affects most other Elasticfox users as well.

I patched HMACQuerySecurityHandler.java to use XMLGregorianCalender instead of using SimpleDateFormat class. This is a simple solution, I guess.

It works for me with Elasticfox, too, but with euca2ools the Timestamp parameter doesn't end with 'Z', so I have to specify GMT timezone again. It's not cool.

The Timestamp without 'Z' does not meet the specs of AWS, does it?
Maybe it depends on boto library...