All Classes and Interfaces
Class
Description
Class called to handle incoming notify service requests.
Class to represent a calendar-query calendar-data element
These are the system properties that the server needs to know about,
which depend on the authenticated state.
This class implements a namespace interface for the webdav abstract
servlet.
Class to represent a caldav node.
Information about properties returned in an XRD object for the restful
protocol
This class extends the webdav servlet class, implementing the abstract
methods and overriding others to extend/modify the behaviour.
Class to represent a calendar in caldav.
Class to represent a collection in CalDAV
Simple implementation of class to represent a collection in CalDAV, used
by the simpler interfaces.
Class to represent an entity such as events in caldav.
Class to represent an event/journal/task in CalDAV
Class to represent a group in caldav.
Retrieve and process CalDAV header values
Class called to handle POST for CalDAV scheduling.
Class to represent a user in caldav.
Class called to handle CalDAV REPORT.
Class to represent a resource in CalDAV
Class to represent a resource such as a file.
These are the system properties that the server needs to know about, either
because it needs to apply these limits or just to report them to clients.
We map uris onto an object which may be a calendar or an
entity contained within that calendar.
Class to represent a user in caldav.
Class extended by classes which handle special GET requests, e.g.
Class to represent a calendar-query filter
Handle freebusy GET requests.
Class extended by classes which handle special GET requests, e.g.
This class provides information about a host.
Handle ischedule GET requests.
An incoming iSchedule message
Class called to handle MKCOL
This type of object will handle system dependent properties through the
system interface.
Allow callers to specify which set of properties are to be processed
Handle freebusy GET requests.
Class extended by classes which handle special SOAP requests, e.g.
Unpack the headers and body
This represents an active connection to a synch engine.
This is a simple bean to handle the dynamic connections made between the
CalDAV server and synch engines.
Handle the dynamic connections made between bedework and synch engines.
Class extended by classes which handle special GET requests, e.g.
Class to represent an RFC icalendar object converted to an internal form.
All interactions with the underlying calendar system are made via this
interface.
Expected result type
What method do we want emitted
Result for a single recipient.
Data for Synch Report
The changed entity may be an event, a resource or a collection.
Show the outcome of an update
Not sure why we need this - perhaps just for tracing?
Handle web calendar GET requests.