This schema fragment defines the error codes and types for use by the
CalWS SOAP web service.
Message from service indicating an error.
Attempted to carry out a forbidden operation.
This may not be possible...
The supplied href does not reference an existing resource.
The supplied href does not target an entity. For example a fetch item
was attempted against a collection.
The supplied entity is not calendar data.
The supplied entity does not represent valid calendar data.
The supplied entity does not represent valid calendar data.
Indicates that the calendar collection does not accept components of the
type the client is attempting to store. The accepted component types can
be determined by examining the calendar collection properties.
Error indicating at least one of two conditions:
1) the server does not allow the creation of calendar collections
at the given location in its namespace, or
2) the parent collection of the Request-URI exists but cannot accept members;
Error indicating that the total size of the event or task is too large.
The maximum date is set by the target system and can be determined
from the properties.
Error indicating that the start or end of an event or task is too
far into the past.
The minimum date is set by the target system and can be determined
from the properties.
Error indicating that the start or end of an event or task is too
far into the future.
The maximum date is set by the target system and can be determined
from the properties.
Error indicating that a recurring event has too many instances.
The maximum number is set by the target system and can be determined
from the properties.
Error indicating that a scheduling message has too many attendees.
The maximum number is set by the target system and can be determined
from the properties.
Indicates that a MultiOpType operation was partially successful. Returned
when the operation is marked as non-atomic and one or more sub-operations
failed. The entire response needs to be examined to determine which
operations failed.
An operation was attempted which required a change token but none was
supplied.
Note that it appears that the marshalling or demarshalling should handle
this as the token is required. It doesn't.
An update operation was attempted with a change token value which does not
match that held by the service. The client must refetch the entity to
refresh its cached value and token.
Note that matching of tokens is a server responsibility. The token is
opaque to the client but probably structured to the server. Certain
non-conflicting updates may be allowed even if the token has changed.
An attempt was made to store an entity which would result in more than
one entity having equal uids. The entity uid must be unique within a
collection. Recurring event or tasks overrides have the same uid and are
considered part of a single entity.