Uses of Package
org.exoplatform.caldav.model
Packages that use org.exoplatform.caldav.model
-
Classes in org.exoplatform.caldav.model used by org.exoplatform.caldav.modelClassDescriptionA declared server's provider configuration as the administration screen may see it: the stored values with every secret left out, and which secrets have a value stored.What kind of owner a calendar shared with the user belongs to (EXO-90275): a person, or a resource such as a room or a pool vehicle.Who an eXo personal calendar is shared with on its CalDAV server, as the server's access control list says at the moment of asking (EXO-90253).One principal a calendar is shared with.Which of BlueMind's two kinds of published link a calendar was published as.What a principal's entries grant.Who a principal on a calendar's access list is, to eXo.An eXo user, as a sharee or a candidate.Why a pair is
CalendarSyncStatus.PAUSED.The lifecycle of one calendar pair.Where an administrator wants the meeting copies of a server to land.What one pass over the copies eXo pushed found, and what it did about it.What eXo still owes one calendar copy.What eXo still owes a colleague's BlueMind account about one shared calendar (EXO-90277).A calendar of the connected account, in the shape agenda expects from any connector.What listing the connected account's calendars actually produced, failures included.What reading the connected account over a period actually produced, failures included.One occurrence read from a remote calendar, in the shape agenda displays.The behaviours a CalDAV server can be excused for, named in code.Which way a divergence between a copy and what eXo writes points.What ticking a quirk actually does — and the two answers are not the same kind of thing.Which side of the pair created the collection, and therefore which side owns its existence.Through which door eXo writes and removes the meeting copies of a server. -
Classes in org.exoplatform.caldav.model used by org.exoplatform.caldav.service