Package org.exoplatform.caldav.plugin
package org.exoplatform.caldav.plugin
-
ClassDescriptionA 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).The owner of every calendar an account's session sees, as the server answers it: what the owner cache keeps per account.What a calendar server product adds to the plain CalDAV the host speaks: which registrations are that product's, the write channels it may use besides CalDAV, and the per-account sessions it keeps outside the protocol.A server-specific way of sharing a calendar collection with a colleague, for a server on which the host's built-in mechanism — RFC 3744's
ACLmethod — is not how the server's own users share, and whose every change the contribution can confirm by reading it back.A subscription a collection's name revealed: whose calendar it is.How a calendar server product lays out, and lets eXo edit, the calendars an account subscribes to — the calendars of somebody else that its DAV listing shows under the account's own home, and that a share only reaches once the colleague is subscribed.A door, other than CalDAV, through which the copies of a server whose registration declares a givenWriteChannelare written and removed.The collection eXo copies space events into, which no channel may take for a user's own calendar.The subscription channel of an account no contributed channel recognises: no subscription is read in its listing, and nothing can be edited.The flavour of a registration no contributed flavour recognises: a plain CalDAV server, which writes through CalDAV only and keeps no session of its own.A calendar of the caller's being shared, resolved and checked by the host: the caller owns it in eXo, their account is connected, and it is bound to a collection eXo created or to an imported one.What the host lends aCalendarShareChannelfor one operation: the lock serialising edits of a collection's access, who eXo knows behind a principal, and the subscription follow-up of a confirmed change.A colleague checked by the host for sharing: an active eXo user, not the caller, connected to the same server registration under a recorded principal that is not the caller's.The reasons a share channel refuses to read, grant or revoke a share: the codes aCaldavShareExceptionor anIllegalArgumentExceptioncarries back to the owner.The edits one session opened as a user can make to the calendars that user subscribes to.