Looks like I forgot the link, anyway, the Commit can be found here:
https://github.com/TheAntimist/openmeetings/commit/e09a8162a9a12f11c843f64775cfda1616988f11
All the CalDAV classes are placed under:
org.apache.openmeetings.service.calendar.caldav
They can be found here:
https://github.com/TheAntimist/openmeetings/tree/3.2.x/openmeetings-service/src/main/java/org/apache/openmeetings/service/calendar/caldav
On 06/17/2016 07:57 PM, Ankush Mishra wrote:
As stated earlier, since my exams are happening my pace has reduced.
With respect to the client Create, Delete and Updation on the CalDAV
Server, now works and has been included in CalendarManager.
Along with that there has been an amount of testing that has taken
place on DAViCal CalDAV Server, on my local server, and Yahoo CalDAV
server. Both have been tested to work, for creation, deletion and
updation of events. Along with proper syncing from the Calendar Server
and local Database. Though, sometimes, I get a bit of JPA updation not
occurring only for *OmCalendar *objects, but Appointment updations and
the rest work fine. I have to fix this, only the persistence aspect,
but otherwise, everything else should work as expected.
Also, I had stated previously that I would use the Appointment.iCalID
for storing etags, but this causes trouble with the iCal MailHandler
and even during creation of events as iCalID is supposed to be
immutable, where as etags are mutable, and uniqueness property of
etags, may not hold always. Thus now, I have added a new field for ETag.
Future Work:
* Add a bit more cases for Parsing of iCalendar.
* Implement Digest Authentication, and if possible also, implement
OAuth.
* Implement a better version of Calendar Service Discovery
* SetUp encryption of OmCalendar passwords.
* Wicket UI.
--
Ankush Mishra
--
Ankush Mishra
