org.outerj.daisy.repository
Class RepositoryException
java.lang.Object
java.lang.Throwable
java.lang.Exception
org.outerj.daisy.repository.RepositoryException
- All Implemented Interfaces:
- Serializable
- Direct Known Subclasses:
- AccessException, AuthenticationException, AuthenticationFailedException, BranchNotFoundException, CollectionDeletedException, CollectionNotFoundException, ConcurrentUpdateException, DocumentLockedException, DocumentNotFoundException, DocumentTypeInconsistencyException, DocumentTypeNotFoundException, DocumentVariantNotFoundException, FieldTypeNotFoundException, GlobalPublisherException, LanguageNotFoundException, NamespaceNotFoundException, NavigationException, PartTypeNotFoundException, PublisherException, QueryException, TaskException, UserManagementException, VersionNotFoundException, WorkflowException
public class RepositoryException
- extends Exception
Thrown if something goes wrong in the repository.
- See Also:
- Serialized Form
|
Method Summary |
Map<String,String> |
getState()
Exceptions which can externalize their state as a map containing
string-string pairs can override this method to do so. |
| Methods inherited from class java.lang.Throwable |
fillInStackTrace, getCause, getLocalizedMessage, getMessage, getStackTrace, initCause, printStackTrace, printStackTrace, printStackTrace, setStackTrace, toString |
RepositoryException
public RepositoryException()
RepositoryException
public RepositoryException(String message)
RepositoryException
public RepositoryException(String message,
Throwable cause)
RepositoryException
public RepositoryException(Throwable cause)
getState
public Map<String,String> getState()
- Exceptions which can externalize their state as a map containing
string-string pairs can override this method to do so. In that
case, they should also have a constructor taking a Map as argument
allowing reconstruction of the exception.
This is used to reconstruct server-side exceptions in the repository
client.