Comment #6 on issue 1561 by [email protected]: Rework/Clean up Times in
Calendar Handling Server Side
http://code.google.com/p/openmeetings/issues/detail?id=1561
This issue was updated by revision r4515.
All references that use some calculation to re-calc the timezones with some
offset is gone now. The time in the database is now in the locale of the
server again and all dates that are printed to the client use the proper
way with SimpleDateFormat. There is a single workaround to parse a client
date to a correctly initialized date on the server.
Backup Import/Export needs to be fixed to include a TimeStamp as long
instead of Date (using a new attribute)
--
You received this message because you are subscribed to the Google Groups
"OpenMeetings developers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/openmeetings-dev?hl=en.