search

Neseek77 / openmeetings

Automatically exported from code.google.com/p/openmeetings
1 stars 0 forks source link

Rework/Clean up Times in Calendar Handling Server Side #1561

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
There is currently an issue in the handling of calendar events:

The times in the tables are stored in UTC.
But the table-data itself has NO timezone info.
If you get the record from the tables, you would need to pre-initialize the 
Date-Objects with UTC-0. 

That means if you get the data from the appointment it is GMT (or whatever 
locale you have) again. 
I do workaround that problem by calculating the offset manually and comparing 
this date. Actually that needed quite a bit of testing.
This can be quite misunderstanding ... 

We should clean up those calculations.

Original issue reported on code.google.com by seba.wag...@gmail.com on 30 Oct 2011 at 5:37

GoogleCodeExporter commented 8 years ago 
This issue was updated by revision r4500.

add new test file for Scheduler Testing in Reminder calculations
Update issue -1
used TypedQuery instead of Query

Original comment by seba.wag...@gmail.com on 31 Oct 2011 at 3:22

GoogleCodeExporter commented 8 years ago

Original comment by seba.wag...@gmail.com on 31 Oct 2011 at 3:22

GoogleCodeExporter commented 8 years ago 
Issue 1346 has been merged into this issue.

Original comment by seba.wag...@gmail.com on 1 Nov 2011 at 12:17

GoogleCodeExporter commented 8 years ago 
Issue 1230 has been merged into this issue.

Original comment by seba.wag...@gmail.com on 1 Nov 2011 at 12:17

GoogleCodeExporter commented 8 years ago 
We will refactor to store the utc times in the database as Long/TimeStamp 
That way we do not loose the timezone information as the timezone is always UTC.

Original comment by seba.wag...@gmail.com on 1 Nov 2011 at 3:31

GoogleCodeExporter commented 8 years ago 
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)

Original comment by seba.wag...@gmail.com on 6 Nov 2011 at 1:53

GoogleCodeExporter commented 8 years ago

Original comment by seba.wag...@gmail.com on 31 Jan 2012 at 12:23

GoogleCodeExporter commented 8 years ago 
OpenMeetings moves to Apache Foundation, update your bookmarks to the new 
project page:

http://incubator.apache.org/openmeetings/

New Issue tracker is located: https://issues.apache.org/jira/browse/OPENMEETINGS

New Mailing Lists located at: 
http://incubator.apache.org/openmeetings/mail-lists.html

Original comment by seba.wag...@gmail.com on 31 Jan 2012 at 12:25