| Overview | Package | Class | Tree | Deprecated | Index | Help |
|
|
||||||||
| PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES | ||||||||
See:
Description
| Interface Summary | |
|---|---|
| BackupService | Provides a Service that
will automatically backup all registered
Restoreable instances
(OSGi white-board model). |
| ExecutionService | Provides a Service for
asynchronous execution of tasks. |
| MailService | Defines the contract for a simple mail service. |
| MaintenanceService | Provides a Service that
will automatically invoke maintenance for all registered
Maintainable instances
(OSGi white-board model). |
| SessionService | Provides a Service for
session handling in stateless contexts (e.g. |
| Exception Summary | |
|---|---|
| MailServiceException | Exception thrown by the MailService if an operation fails. |
Provides the system services interfaces.
These services provide some basic system level functionality for the Coalevo Platform.
Data backup is an essential element to provide smooth and
ongoing operations despite of hardware or system failures.
The BackupService provides the
means for backing up data provided by other services.
The design of the mechanism is based on the white board model:
Services can register a Restoreable
implementation that will automatically be included in the
configured backup process.
Implementations of
Restoreable should allow to backup
the actually used data on-the-fly.
The service should as well handle the restore process in the unlucky case
of a hardware or system failure. Implementations of
Restoreable should allow to restore
the actually used data on-the-fly.
The ExecutionService provides
the ways and means for other services to execute asynchronous tasks
one or more times (i.e. periodical) with or without initial delay.
Services require authentication and authorization to use this service.
Data and System integrity is another essential element for smooth
and continuous operation. The MaintenanceService
provides the operational ways and means to periodically run maintenance tasks
like database cleanup.
The design of the mechanism is based on the white board model:
Services can register a Maintainable
implementation that will automatically be included in the
configured maintenance process. Implementations of
Maintainable should allow
to do this on-the-fly.
The SessionService
provides the operational ways and means manage sessions in
a stateless context (e.g. Web services).
Sessions are volatile, but they can be shared with other services to create
something like a single-sign-on.
|
|
||||||||
| PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES | ||||||||