The following diagram describes the relationships of the API classes that manage session workload.
Client applications and services can throw two types of exceptions, FailureException and FatalException. This diagram shows how they relate to the base exception class, SoamException.
Base class of exceptions the system generates. Can be accessed by client applications and services
Exception thrown to indicate a non-fatal error has occurred in a service. The action taken in the event of a FailureException is dependent on the API method that the exception is thrown in.
Exception thrown to indicate a fatal error has occurred in a service. The action taken in the event of a FatalException is dependent on the API method that the exception is thrown in.
Implements all the required methods to allow the system to interact with the service instance
Provides functionality that the service requires throughout its lifetime
Hosts information that may be required while servicing a task from a session