Class CaldavPushException
- All Implemented Interfaces:
Serializable
The codes are the connector's own — caldav.error.credentials,
conflict, save, noCalendar,
calendarCreationRefused — kept identical on purpose. The browser
stops building iCalendar in this PR but keeps rendering the failures, and a
renamed code would silently degrade every one of them into the generic
message.
Not every code is a failure, whatever this class is called. Some describe a
state of the subject that no retry changes — a user who never connected an
account, one who has not said where their copies go — and those are recorded
at debug, without a trace, rather than as incidents nobody can act on.
CaldavPushService.isKnownState(java.lang.String) draws the line, and a code left out of
it is a failure: see the two sets declared under the vocabulary there, which
a new code has to join one of.
- See Also:
-
Constructor Summary
ConstructorsConstructorDescriptionCaldavPushException(String code, String message) CaldavPushException(String code, String message, Throwable cause) -
Method Summary
Methods inherited from class java.lang.Throwable
addSuppressed, fillInStackTrace, getCause, getLocalizedMessage, getMessage, getStackTrace, getSuppressed, initCause, printStackTrace, printStackTrace, printStackTrace, setStackTrace, toString
-
Constructor Details
-
CaldavPushException
- Parameters:
code- the stable failure codemessage- what went wrong, for the log
-
CaldavPushException
- Parameters:
code- the stable failure codemessage- what went wrong, for the logcause- the underlying failure
-
-
Method Details
-
getCode
The stable code the front end matches on.- Returns:
- the code
-