Package com.saperion.exception
package com.saperion.exception
This package contains the classes for the global exceptions.
-
ClassDescriptionThis exception indicates that something went wrong concerning document definition constraints.This exception indicates that something went wrong concerning a specific data source.This exception indicates that a given data source is offline while it was intended to be used.This exception indicates that an entity was encountered whose data is in some way malformed or inconsistent.This exception indicates that a mandatory constraint for a given list of fields in a given ddc was violated.Utility class for mapping return codes to exceptionsThis exception is thrown when the system detects an attempt to modify an entity that is not a latest revision..This
Exceptionindicates that evaluating a query failed.Authentication exceptions which may occur in the following situations.
Authentication
"system failure during log on process", "user does not exist", "wrong password", "user account is inactive", "no current user for automatic login found", "client was not supplied", "no licenses available for login", "user account is already in use", "password has expired", "invalid client kind", "user is not logged in".Barcode exception.Base exception.Exception is thrown when a (re) connect to RMI server failed.Exception, thrown during the query execution (connector level).DDC related exception raised in the following situations:
//GetDefinitions "DDC files could not be retrieved",
//GetFields "database definition could not be opened", "database definition invalid, possibly empty DB mappings or invalid data source".Exception thrown when a folder is created and a sibling with the same name already exists.Exception, thrown during folder related errors (connector level).Exception thrown in folder-related methods when a folder name contained an invalid character.Thrown when an operation with folders is not allowed.* Exceptions in getting node or content; occur in the following situations: "creating document structure in memory failed", "loading document metadata failed", "loading sub-document from structure failed", "loading document content failed", "invalid document handle was provided", "no document content available", "accessing document handle failed", "accessing document content failed", "given byte offset is greater than data size", "document uid is empty", "document member is empty", "unsupported document type encountered", "initializing index data array failed", "archiving new document failed", "committing transaction failed", "rolling back transaction failed", "transaction ID is invalid/empty", "updatind document content on medium failed", "updatind document metadata in database failed", "deleting document failed", "retrieving database cursor failed".Exception thrown by SaImageConverter if converting an image failed.JCR related Base exception.This exception is thrown when a user logs on with a license that he is not allowed to use because of missing privileges.* Lock exceptions which occur in the following situations: "locking or unlocking document failed", "document is currently locked by another user", "retrieving lock data failed, possibly unavailable".Deprecated.Deprecated.Indicates that the users password is expired.This exception indicates that the saperion system is not configured to handle the method call properly.Exceptions in JCR Properties; occurs in the following situations: setting document property failed, column/property name does not exist, invalid database definition name specified, improper index element count specified for field type, binary data section (lob) is empty, unsupported property type specified.Exception thrown when checking a SAP-URL failed.SaSearchFieldException will be thrown in case of a data base field cannot be found.Exception class for RMI security exceptions.SaSetACLException will be thrown in case of a ACL could not be set in the backend.Exceptions in setting content, occur in the following situations: "creating temporary file failed", "making up temporary file name failed", "handle to temporary content file is invalid", "writing buffer to content file failed", "inserting content into document failed", "closing temporary file failed".Exceptions in setting or deletion node; occurs in the following situations: "committing transaction failed", "rolling back transaction failed", "transaction ID is invalid/empty", "updating document content on medium failed", "updating document metadata in database failed", "deleting document failed", "given byte offset is greater than data size".Exception class for common system errors and some failed RMI commands.This exception is thrown when a query returned more results than allowed.Exception thrown when a document is created or updated and the value of a unique field already exists in another document.Exception thrown when a folder type is unknown.Will be thrown if that calculated hash or length of the content stream does not match the expected values.This exception indicates that a call tried to write to a system field directly.This exception indicates that a uniqueness constraint for a given list of fields in a given ddc was violated.This exception indicates that a given data source could not be found.This exception indicates that a given document definition could not be found.Indicates that for a given reference, there was no match found.Will be thrown if a SerializableStream exceeds its length-limit (as given by the ContentStream to serialize).This exception is intended to wrap instances ofSaBasicExceptionin order to transport them by rmi without breaking compatibility of existent calls andoperations.This exception works as wrapper in cases where server components already throw new exceptions while the client interface still expects the old ones.This exception indicates that the type of a document definition does not work the way it is used.