Hi, I have just recently upgraded from 3.5.x to 3.6.x. However, the behavior of saving of a Calendar object is very different.

In 3.5.x, the time saved to the database is in the timezone of the Calendar object. In 3.6.x, the time saved to the database is always the time converted to the timezone where I run my process.

For example, I create a Calendar object in the GMT timezone set at 7pm. In 3.5.x, the time saved to database is 7pm. However, in 3.6.x, the time saved to the database is 2pm, if I run the process in eastern timezone. It would be 1pm, if I run the process in central timezone.

Does anyone know if this behavior is done intentionally? Is there annotation that I can use to get the old behavior back?

Many thanks in advance.