fesa-core  7.0.0
Class Hierarchy
This inheritance list is sorted roughly, but not completely, alphabetically:
[detail level 1234]
oCfesa::AbstractComponentEquipmentThis class is an abstraction of the components of an equipment. It contains common services shared by both the server and real time parts
oCfesa::AbstractDeviceClassEach instance of this class represents a FESA-Class (XML-Design-Document)
oCfesa::AbstractDeviceFactoryThis abstract class contains virtual methods to create the devices on the system
oCfesa::AbstractEquipmentThis class is the head of each equipment. It is used to decouple the server and the RT package from the core package
oCfesa::AbstractEventAbstract Base class of the two concrete Events: RequestEvent and RTEvent This class cannot be instantiated and it contains only common services
oCfesa::AbstractEventSourceFactoryThis factory provides methods to handle events sources
oCfesa::AbstractFieldBase class which defines virtual methods to manage all the FESA fields
oCfesa::AbstractMessageA message that can be transmitted on a message queue
oCfesa::AbstractMsgQueueAn abstract message queue. The concrete implementation (the STL queue or the IPC queue) depends on the deployment mode (mixed or split)
oCfesa::AbstractMultiplexingManagerThis class is used to find the correct slot for a multiplexed field value using the virtual accelerator or the multiplexing context
oCfesa::AbstractRTActionFactoryThis class provides a method to create AbstractRTActions by their configuration and name
oCfesa::AbstractServerActionThis is the based class for all the server actions in the system which will be executed when a property is requested. TODO discuss the DataType parameter
oCfesa::AbstractServerActionFactoryThis class is responsible to provide a method in order to create the server actions for the class
oCfesa::AbstractServerControllerThe AbstractServerController manages the proper startup and shutdown of all services, providet by the server side
oCfesa::AbstractUserDiagnosticsUser side diagnostic infrastructure
oCfesa::AcqFieldHistory< FieldType, HistoryFieldType >
oCfesa::AcqFieldHistory< AcqFieldFunction, GenericFieldFunction >
oCfesa::AcqFieldHistory< AcqFieldFunctionList, GenericFieldFunctionList >
oCfesa::AcqFieldHistory< AcqFieldScalar< T >, GenericFieldScalar< T > >
oCfesa::AcqFieldHistory< AcqFieldScalarArray2D< T >, GenericFieldScalarArray2D< T > >
oCfesa::AcqFieldHistory< AcqFieldScalarArray< T >, GenericFieldScalarArray< T > >
oCfesa::AcqFieldHistory< AcqFieldString, GenericFieldString >
oCfesa::AcqFieldHistory< AcqFieldStringArray, GenericFieldStringArray >
oCfesa::AcqFieldHistory< AcqFieldStruct< T, MutableType >, GenericFieldStruct< T, MutableType > >
oCfesa::AcqFieldHistory< AcqFieldStructArray2D< T >, GenericFieldStructArray2D< T > >
oCfesa::AcqFieldHistory< AcqFieldStructArray< T >, GenericFieldStructArray< T > >
oCfesa::AcquisitionFieldCommon
oCfesa::Functors::AddPointee< T >
oCfesa::Aligned< T >
oCds::AnyError
oCfesa::Array2DRow< T, runtimeCheck >
oCfesa::ServerData::Array2DSizeRepresentation of the size of a two-dimensional array
oCfesa::ServerData::ArraySizeRepresentation of the size of a one-dimensional array
oCfesa::AsyncGetCallback
oCfesa::Atomic< T >
oCfesa::Atomic< uint32_t >
oCfesa::AttributeXMLThis class represents an XML attribute containing name and value
oCfesa::ClassElementUsed to store all class-related Information from the Instantiation-File
oCfesa::Functors::CompareToReferenceOrder< T, InputIterator >
oCComplementExpressionThis class extends the sorting expression in order to check if the context matches the negated expression
oCfesa::ConcurrentQueue< T >
oCfesa::ConcurrentQueue< boost::shared_ptr< fesa::RTEvent > >
oCfesa::ConditionalVariableThis class is a c++ wrapper in order to use conditional variables. Conditional variables help to synchronize threads when there's a logical condition for the synchronization
oCfesa::ContextData
oCfesa::ControllerFactory
oCfesa::Converter< T >Conversion of values of arbitrary types to strings and vice versa
oCfesa::ConverterArray< T >Class that contains conversion method to convert array data
oCfesa::ConverterArray2D< T >Class that contains conversion method to convert array2D data
oCfesa::ConverterStringArrayClass that contains conversion method to convert string-array data
oCfesa::CycleDescriptorThis class provides an interface to retrieve the cycles ids and names depending on the timing domain. Since the timing Domain is lab specific, a child class inside the lab package implements most of the methods
oCfesa::CycleSelectorThis struct represents a cycle selector composed of timing domain, multiplexing criterion and the line
oCfesa::DataManager
oCfesa::DataStoreBase class for field-storage classes in the framework: Device, GlobalDevice and DomainStore
oCfesa::DataStoreElementUsed to store all data-store-specific information which comes from the instance-file
oCfesa::DeploymentThreadConfigurationA class to retrieve a thread's scheduling configuration (its priority and affinity). A thread's scheduling configuration is retrieved either from the deployment unit's design (if it's specified there), or from the framework (the default configuration). If information about a thread's priority or affinity is available in the deployment unit's design, the member function corresponding to the thread has to be overriden in the generated derived class
oCfesa::DeviceFactoryImp< GlobalDeviceType, DomainStoreType, DevInstType >The DeviceFactory is designed as a bridge pattern to allow sub-classing of the class interface (DeviceFactory) and the class implementation (this one) separately. This DeviceFactoryImp is the abstract-class that declares the interface to the underlying device-factory implementation (Shm, Heap). It instantiates all devices, global-device, domain-store and initializes everything
oCfesa::DeviceInstantiationDataThis class facades the class "DeviceElement" in order to provide a simple API for class-developers and to hide methods which were made for internal usage
oCfesa::DeviceLogicalEventElementUsed to store all Device-LogicalEvent-specific Information which comes from the Instantiation-File
oCfesa::DiagnosticsDefs::DiagnosticMessageA message collecting information needed for diagnostics
oCfesa::DiagnosticUtils::DiagnosticMessageDiagnostic message
oCfesa::DiagnosticsDiagnostic infrastructure
oCfesa::DiagnosticsDefs::DiagnosticsEventPayloadDiagnostics setting information passed from the server part to the RT part needed to set up diagnostics
oCfesa::DiagnosticsDefs::DiagStateCounterDiagnostic state counting information To be reviewd with FESA-2973
oCfesa::ElementXMLThis class represents an XML element containing name, value, a list of attributes and a list of child XML elements
oCEquipmentDeviceThis class contains different information necessary to access from the Real time and the Server packages
oCfesa::EventConfigurationElementUsed to store all EventConfiguration-specific Information which comes from the Instantiation-File
oCfesa::EventElementUsed to handle and store all Event-specific Information which comes from the Instantiation-File. This class is Abstract
oCfesa::ExporterFactoryThis class provides functionality for creation and storage of notification exporters
oCfesa::FesaExceptionThis class is the based class for all the exceptions in the FESA framework. It contains an error code in order to retrieve the message linked to the error. This error code has to be in the messages.cfg file The class also admits parameters to be replaced in the message in the format $1,$2 ..
oCfesa::FieldCallback
oCfesa::FieldConfigConfiguration information needed for field construction
oCfesa::FieldElementImplImplementation of pure virtual class FieldElement
oCfesa::FieldSynchroManagerClass that manages the synchronization of persistent fields
oCfesa::FrameworkDiagnosticsFramework side diagnostic infrastructure
oCfesa::FunctionIterator< FunctionType, LocalFunctionType >
oCfesa::FunctionIterator< const ImmutableFunction, ImmutableFunction >
oCfesa::detail::FunctionStorage
oCfesa::HasMetrics
oCfesa::HomogeneousDevColThis class contains a collection of devices and it lets do operations between other collections like add up, or rest
oCfesa::ImmutableArray< T, runtimeCheck, ArrayImpl >
oCfesa::ImmutableArray2D< T, runtimeCheck >
oCfesa::ImmutableArray< T, runtimeCheck >
oCfesa::ImmutableFunction
oCfesa::ImmutableFunctionList
oCds::InvalidDataValue
oCds::InvalidFilterValue
oCfesa::Functors::LessOnPointees< T >
oCfesa::SortingLexer::Lexeme
oCfesa::LockThis class is used to automatically lock and unlock a mutex. The constructor calls lock() and the destructor calls unlock(). This makes it impossible to leave a block containing a Lock object without unlocking the mutex. The mutex can also be unlocked explicitly, by calling the unlock() method
oCfesa::LogicalEventAbstract base-class for the LogicalEvent
oCfesa::LogicalEventElementUsed to handle and store all Logical-Event-specific Information which comes from the Instantiation-File
oCMannualNotificationMessageA message type used for manual property notification
oCfesa::Metric
oCfesa::MetricsManager
oCfesa::ModifiedField
oCfesa::MultiplexingContextThis class contains the information used for multiplexed fields
oCfesa::Mutex
oCfesa::MuxSubscriptionMatcher
oCds::NoDataAvailable
oCds::NoDataAvailableForUser
oCfesa::SortingParser::Node
oCfesa::NotificationExporter::NotificationEvent
oCfesa::NotificationIDThis class provides an unique notification identifier. The ID is generated from the className, the devices specified by the selection criterion, and the properties that will be notified
oCNotificationIDGeneratorThis class generates the notification id collection
oCfesa::NotificationThreadFactory
oCfesa::OnFaultNotificationConfigConfiguration information needed to set up the on-fault notification
oCfesa::PersistanceDataStoreElement
oCfesa::PersistanceFieldSlot
oCfesa::Pipe
oCfesa::Point
oCfesa::wrappers::PointerWrapper< T, CallbackType >
oCfesa::PointIterator< PointType >
oCfesa::PointIterator< const Point >
oCfesa::ProcessConfigurerTake care of configuring the FESA process from either configuration files or command line arguments
oCfesa::ProcessStackTrace
oCfesa::PropertyThis class represents a property which computes through server actions the value of a requested attribute
oCfesa::PropertyBuilderUsed to build Properties. Can be extended in order to build lab-specific properties
oCfesa::PropertyConstructorParameters
oCfesa::PropertyInfo
oCfesa::FaultField< DataType >::PropertyNotifierRaising and lowering a fault field may automatically notify some lab-defined properties that display information about faults. Lowering a fault field should notify the properties whose get server actions were disabled by this field
oCfesa::ProxyInterfaceInterface to access device properties with set, get or subscription calls. This class is meant to be used as the implementation of an association relationship between classes. It could be also used to establish association relationships between devices of the same class. Therefore a class can access a device of the same class or different class deployed on the same or on a different frontend
oCfesa::ProxyReplyHandlerAn instance of ProxyReplyHandler is passed as a reference to the Middleware when performing a subscription. The middleware then uses it as a callback
oCfesa::QueueLimitsLimit parameters of message queues
oCfesa::RangeChecker::Range< T >Representation of a range of values
oCfesa::ReadLockThis class is used to automatically lock and unlock a read-write lock for reading. The constructor acquires a read-lock. The destructor releases the lock if it has not been explicitly unlocked. This ensures the read-write lock is returned to its previous state when a ReadLock object leaves scope. The read-write lock can also be unlocked explicitly, by calling the unlock() method
oCfesa::RollingBufferMuxDataManagerThis class provides methods to retrieve information about the cycle IDs and names that a multiplexing manager uses regardless the implementation of the data. The prefix "rolling" means the following: 1.) The number of available slots can be defined per class-instance. 2.) Only acquisition data is handled by the rolling data manager. 3.) New values are written inside just one after another for all incoming cycles(cycleNames) 4.) If the last slot is reached, the rolling data manager will continue writing on the first slot. 5.) It is possible that for an "old" cycle no data is available, since it was already overridden
oCfesa::RTActionConfigThis structure stores all the necessary information to configure an action
oCfesa::RTControllerThis class configures the real time process. It creates the event sources, actions, and schedulers and configures those elements so that the real time part is ready. The class is also responsible for starting the event sources and schedulers
oCfesa::RTEventPayloadIt is meant to carry the payload of an Event
oCfesa::RTLayerInfo
oCRTSchedulingInfoThis structure contains the information from the design document necessary to create the schedulers
oCfesa::RTSchedulingUnitRef
oCfesa::RWLock
oCfesa::DeploymentThreadConfiguration::SchedulingConfigA thread's scheduling configuration
oCfesa::ThreadConfigurer::SchedulingConfigA thread's scheduling configuration, i.e. its priority and its affinity
oCfesa::SelectedDeviceCollection
oCfesa::SemaphoreThis class is a wrapper around POSIX semaphores
oCServerActionDesignConfigThis structure contains the attributes to configure the action.These attributes come from the design document
oCfesa::ServerDataThe framework's abstraction of a property's data or of a property's data filters. It provides access to the "raw" CMW data for get and set requests
oCfesa::SettingFieldsReadGuard
oCfesa::SharedMemoryAllocator
oCSingletonBase< T >This class can be inherited by singletons to provide thread-safe instantiation and guaranteed destruction upon normal process exit
oCSingletonBase< MsgQueueFactory >
oCSingletonBase< NotificationIDManager >
oCfesa::SortingContext
oCfesa::SortingExpressionThis is the base class which defines sorting expressions in the sorting package. It defines the match method in order to find out if the expression matches the context
oCfesa::SortingLexer
oCfesa::SortingParser
oCfesa::StackTrace
oCfesa::StoreManagerThis class is responsible for storing and restoring devices of a class from a persistency mechanism
oCfesa::ServerData::StringArray2DSizeRepresentation of the size of a two-dimensional array of strings
oCfesa::ServerData::StringArraySizeRepresentation of the size of a one-dimensional array of strings
oCfesa::SynchronizationLabObjectFactoryThis class provides methods in order to create the different types of timing descriptors or in general the specific Lab synchronization objects
oCfesa::ThreadThis class is a wrapper in order to manage threads according to the object oriented style
oCfesa::ThreadConfigurerA class to configure the framework's threads' scheduling parameters (their priorities and afffinities). The configuration is done based on the information given in the instantiation file, the deployment unit's design, and the framework itself (the default values)
oCfesa::Watchdog
oCfesa::WriteLockThis class is used to automatically lock and unlock a read-write lock for writing. The constructor acquires a read-lock. The destructor releases the lock if it has not been explicitly unlocked. This ensures the read-write lock is returned to its previous state when a WriteLock object leaves scope. The read-write lock can also be unlocked explicitly, by calling the unlock() method
\Cfesa::XMLParserThis class offers functions to extract information from an XML file. It uses the xPath functions of the library libXML