All Classes and Interfaces
Classes
Class
Description
Refreshes the Agenda badge of every attendee concerned by an event change.
Reports how many invitations the user still has to answer, on the Agenda
application tile.
Reads other people's busy time, so that a screen where a meeting is being
scheduled can draw it.
The one place free/busy is computed, and the one place it is guarded.
The digest email lines of the agenda notifications: an invitation to an
event, a new date poll.
A listener that will be triggered when a user reply to an event.
A listener that will be triggered when an event is created or updated.
A listener that will be triggered when updating or creating an agenda event.
This listener will persist occurrences of recurrent event, that will trigger
its reminders before
AgendaEventReminderService.getReminderComputingPeriod() (in days).A job to send reminders of current minutes switch computed
EventReminder.getDatetime()A listener that will be triggered when a new response is sent to an event.
A listener that will be triggered synchronously after saving (create OR
update) an event to change automatically response of users
The one place a schedule clash is decided.
Listener that is triggered when a user sends a vote on an event.
Listener that is triggered when a user sends a vote on an event.
A listener that will be triggered synchronously after saving user reply to an
event to transmit modifications to the end user himself via WebSocket.
A listener that will be triggered synchronously after saving (create OR
update) an event to transmit modifications to end users via WebSocket
A service to push notifications from server to browsers of users about
modifications made by other users on events.
Turns the busy-time domain model into what goes on the wire.
Gives an anchor to the calendars that predate the column holding it.
This Job will be executed to compute exact reminder date for events of next
two days.
What every iCalendar document eXo writes about a meeting says the same way.
A busy range as it leaves the server: two instants, in ISO-8601 with an
offset, and nothing else.
One participant's busy time as it leaves the server, with the status of the
read that produced it.