Associated Components
Represents a set of components (like VEVENT) stored in a calendar object resource as defined in RFC 4791 section 4.1. It consists of
an (optional) main component,
optional exceptions of this main component.
Note: It's possible and valid that there's no main component, but only exceptions, for instance when the user has been invited to a specific instance (= exception) of a recurring event, but not to the event as a whole (→ main event is unknown / not present).
Parameters
main component (with or without UID, but without RECURRENCE-ID), may be null
if only exceptions are present
exceptions (each without RECURRENCE-ID); UID must be
the same as the UID of main,
the same for all exceptions.
If no main is present, exceptions must not be empty.
Throws
when the constraints above are violated