Package org.mbs.services.device.abstractdriver

This package defines the API of the of the Abstract Driver architecture.

See:
Description

Class Summary

AbstractDeviceActivator	This abstract class should be used to implement bundle activators for all device drivers.
AbstractDeviceController	This class is used for super class for all Device controller implementation classes.
AbstractDeviceDriver	Base driver class for all device drivers.
AbstractDeviceModel	Base model class for all device models.
DeviceControlUnit	This class represents a device control unit.
DeviceStateGraph	This class represents device state graph.
TokenDeviceControlUnit	This is the extension of DeviceControlUnit with token mechanism supported.
TracerMaps	TracerMaps.java

Exception Summary

AbstractDriverException

Thrown when a problem occurs in base driver

Package org.mbs.services.device.abstractdriver Description

This package defines the API of the of the Abstract Driver architecture. It supposed to be used by device driver developes and eases the process of implementing a device driver.

The main features of the Abstract Driver are:

• Defines a Model-Controller mechanism, which presents the Device, and provides abstract implementations for such a model and a controller.
• The Device Model represents the internal state of the device. It contains a number of state variables and is responsible to notify the subscribed listeners upon state variable changes.
• The Device Controller offers a set of actions. Invocation of an action is supposed to change the internal state of the device.
• The control unit of the device is composed by both the model and the controller and it is registered as a service into the OSGi framework. The control units allow the applications to access the devices without any notion of the underlying network protocol.
• Create and register a Control Unit service according to the specific device features: controls, events and data.
• Present a common way for the specific drivers to declare their actions and state variables.
• Allow the definition of a state graph for the devices and watch for device model inconsistency.

In other words the Abstract Driver represents a utility API, which is extended by the different protocol drivers, for example EHS Driver. It provides abstract implementation not strictly bound to any kind of devices.