[
https://issues.apache.org/jira/browse/OPENMEETINGS-166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13254318#comment-13254318
]
SebastianWagner commented on OPENMEETINGS-166:
----------------------------------------------
Hi Eugen,
your obections are quite good, with that tipp I was able to reproduce it
finally :)
I was able to solve the problem (I hope at least).
It was wrong thinking, a Date object never has a timezone ..., you might see
commit 1326317
> Meeting is created with incorrect start time in the calendar.
> -------------------------------------------------------------
>
> Key: OPENMEETINGS-166
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-166
> Project: Openmeetings
> Issue Type: Bug
> Components: BuildsAndReleases
> Affects Versions: 2.0 Apache Incubator Release
> Environment: OpenMeetings rev. 1325710
> Reporter: Irina Arkhipets
> Assignee: SebastianWagner
> Attachments: flvRecording_29.flv
>
>
> How to reproduce:
> - Log into OpenMeetings as some user
> - Go to the uset calendar
> - Create a meeting
> Result: meeting is saved with incorrect start time.
> For example, if default server time zone is ETC/GMT+4, start time gets
> shifted on 3 hours back. If I am updating the same meeting once again, start
> time does not shift anymore.
> It seems like this does not depend on the user time zone. It works in the
> same way for the users with ETC/GMT+4 and ETC/GMT+6 on the same server.
> Some time ago I tried this with the server in NSK/GMT+6, and start time was
> shifted to 6 hours.
> Please see attached recording for more details.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
