Uses of Package
com.saperion.exception
Packages that use com.saperion.exception
Package
Description
This package contains the main classic connector classes.
This package contains the classes for the LARIX LDAP Kerberos authentication components.
Package for connector RMI client classes.
This package contains the client-side implementations of services.
This package contains the main classic workflow connector classes.
This package contains the constant definitions for the SAPERION LARIX system.
This package contains the classes for the global exceptions.
This package contains the classes for the workflow exceptions.
This package defines the different operations, that can be invoked by rmi.
This package defines the different operations on documents, that can be invoked by rmi.
This package defines the different operations on folders, that can be invoked by rmi.
This package defines the different operations on lookup tables, that can be invoked by rmi.
This package defines the different workflow-operations, that can be invoked by rmi.
This package contains the classes for the LARIX RMI client wrapper components.
This package contains the classes for the LARIX RMI Server.
This package contains the exception classes for RMI client components.
This package contains the utility classes for the LARIX RMI Server.
-
Classes in com.saperion.exception used by com.saperion.connectorClassDescriptionAuthentication 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.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 during folder related errors (connector level).Exception thrown in folder-related methods when a folder name contained an invalid character.* 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".* 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".Exception thrown when checking a SAP-URL failed.SaSetACLException will be thrown in case of a ACL could not be set in the backend.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. -
Classes in com.saperion.exception used by com.saperion.connector.eventsClassDescriptionAuthentication 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".Exception class for common system errors and some failed RMI commands. -
Classes in com.saperion.exception used by com.saperion.connector.exceptionsClassDescriptionAuthentication 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".Base exception.Exception class for common system errors and some failed RMI commands. -
Classes in com.saperion.exception used by com.saperion.connector.ldapClassDescriptionException class for common system errors and some failed RMI commands.
-
Classes in com.saperion.exception used by com.saperion.connector.rmiClassDescriptionAuthentication 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".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 during folder related errors (connector level).* 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".* 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".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.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.Will be thrown if that calculated hash or length of the content stream does not match the expected values.Will be thrown if a SerializableStream exceeds its length-limit (as given by the ContentStream to serialize). -
Classes in com.saperion.exception used by com.saperion.connector.serviceClassDescriptionBase exception.Exception class for common system errors and some failed RMI commands.
-
Classes in com.saperion.exception used by com.saperion.connector.wfClassDescriptionAuthentication 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".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 class for common system errors and some failed RMI commands. -
Classes in com.saperion.exception used by com.saperion.constants
-
Classes in com.saperion.exception used by com.saperion.exceptionClassDescriptionThis exception indicates that something went wrong concerning document definition constraints.This exception indicates that something went wrong concerning a specific data source.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".Base exception.JCR related Base exception.Exception class for common system errors and some failed RMI commands. -
Classes in com.saperion.exception used by com.saperion.exception.wf
-
Classes in com.saperion.exception used by com.saperion.jna.typemapping.databaseClassDescriptionException class for common system errors and some failed RMI commands.
-
Classes in com.saperion.exception used by com.saperion.operationsClassDescriptionBase exception.Exception class for common system errors and some failed RMI commands.
-
Classes in com.saperion.exception used by com.saperion.operations.document
-
Classes in com.saperion.exception used by com.saperion.operations.folders
-
Classes in com.saperion.exception used by com.saperion.operations.lookupClassDescriptionBase exception.Exception class for common system errors and some failed RMI commands.
-
Classes in com.saperion.exception used by com.saperion.operations.storage
-
Classes in com.saperion.exception used by com.saperion.operations.user
-
Classes in com.saperion.exception used by com.saperion.operations.workflow
-
Classes in com.saperion.exception used by com.saperion.rmiClassDescriptionAuthentication 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".* 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 class for common system errors and some failed RMI commands.Will be thrown if that calculated hash or length of the content stream does not match the expected values. -
Classes in com.saperion.exception used by com.saperion.rmi.commonClassDescriptionAuthentication 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".Base exception.Exception class for common system errors and some failed RMI commands. -
Classes in com.saperion.exception used by com.saperion.rmi.serverexceptionClassDescriptionBase exception.Exception class for common system errors and some failed RMI commands.
-
Classes in com.saperion.exception used by com.saperion.utilClassDescriptionAuthentication 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".Exception thrown in folder-related methods when a folder name contained an invalid character.Exception thrown by SaImageConverter if converting an image failed.Exception class for common system errors and some failed RMI commands.