Uses of Package
org.exoplatform.caldav.service
Packages that use org.exoplatform.caldav.service
Package
Description
-
Classes in org.exoplatform.caldav.service used by org.exoplatform.caldav.clientClassDescriptionThe registry of CalDAV servers a deployment offers its users: what an administrator declares in the third section of the agenda administration page.
-
Classes in org.exoplatform.caldav.service used by org.exoplatform.caldav.listenerClassDescriptionCarries what happens to a meeting in eXo out to the calendars of the people it concerns: a creation to everyone invited, an edit or a cancellation to every copy that already exists, a deletion to every copy that has to go.Enrols a user on the CalDAV server managed mode designated, when they log in (EXO-89653): the login-time attachment the board describes.Writes eXo's space events into the user's remote calendar, server-side.Keeps a user's eXo calendars and their remote collections in step, in both directions.
-
Classes in org.exoplatform.caldav.service used by org.exoplatform.caldav.restClassDescriptionA push that could not be carried out, carrying the machine-readable code the browser already knows how to turn into a message the user can act on.A share of a calendar that could not be read, granted or removed for a reason that is neither the caller's request nor their rights: the account, the server's capability, or the server's own answer (EXO-90253).What the last pass over one user's copies found and moved.Where a user's space events are copied, and how that destination came to be.
-
Classes in org.exoplatform.caldav.service used by org.exoplatform.caldav.serviceClassDescriptionWhat the server itself says about who owns each calendar an account sees — the fourth witness
CaldavOutboundService#ownershipOfhears (EXO-90347), asked at most once per account per pass.The server's word on one calendar, and the owner it named.What the server said about one calendar.Drops the BlueMind REST session an account holds when eXo itself changes what that account is (EXO-90397).What one adoption pass over one object did.A calendar's collection on the caller's server and the shares read from it, both from one resolution of the calendar (EXO-90385).A calendar's collection on the caller's server.Who each connected eXo user is on their CalDAV server, and which eXo users are connected as a given principal (EXO-90243).Deleting a personal calendar, on both sides.What one reconciliation managed.Gives each of a user's eXo personal calendars a collection of its own on the remote server.Writes eXo's space events into the user's remote calendar, server-side.What became of one attempt to write an answer onto one copy.Asks the server whose each calendar in an account's view is — once per account per pass at most, and mostly from a cache (EXO-90347).The registry of CalDAV servers a deployment offers its users: what an administrator declares in the third section of the agenda administration page.Makes a calendar shared from eXo on BlueMind appear to the colleague it was shared with, by subscribing their BlueMind account to it as they would themselves — and removes that subscription when the share is revoked (EXO-90277).What retiring one binding came to.Keeps a user's eXo calendars and their remote collections in step, in both directions.The pieces of outward work a pass may do once the calendars themselves are in step — each named, and each governed on its own.Who a shared calendar belongs to, as far as the viewer may be told (EXO-90237).Whose a listed calendar collection is, to the eXo user whose account listed it — the one answer the sweep, the calendar list and the event read-through all act on, so that they cannot disagree about a collection.What the last pass over one user's copies found and moved.What one relocation pass did to the copies already on the server, and whether the destination change may be recorded as applied.Where a user's space events are copied, and how that destination came to be.