Owner module

The Owner Module is a unique Module which allows the framework to be created and controlled from an external application. Note that:

• Only one Owner module can be defined for all the framework
• If an Owner module is defined, the framework must be called by a Framework Owner
• If the framework is created with a Framework Owner , an Owner module must be defined

Note that the Owner Module only mediates the Services notifications to the Framework Owner. Every call will be deferred to the Framework Owner.

Deployment

This module do not need a deployment in their parent application because the code which will be called is the framework Owner code.

Declaration

This module is declared by the top-level ownerModule element. For example:

      <ownerModule name="FlightManagementSystem" id="1" >

Module implementation

This module do not need an implementation because the code which will be called is the framework Owner code.

Example

In the following example, the framework Owner will be called when a notification from the "position", "directTo", or "computeFlightPlan" Services^[1]

In this last case it would be a request

are received:

      <ownerModule name="FlightManagementSystem" id="1" >
         <interfaces>
            <subscribe service="position" />
            <eventReceived service="directTo"/>
            <requestReceived service="computeFlightPlan"/>
         </interfaces>
      </ownerModule>

Update frequency control

It is possible to control the update rate for Services invoked by an Owner module. It can be useful if the rate of invocations from the external application is too high. This is managed by two default properties in the application properties configuration:

• allServices.updateCap: the default property allowing to set an update cap in ms for all Services for a Module
• publishServices.updateCap: the default property allowing to set an update cap in ms for publish Services for a Module.