Home
Categories
Dictionary
Glossary
Download
Project Details
Changes Log
What Links Here
FAQ
License

Application



Applications are the top-level element of the framework architecture. They contain the executable libraries (jar files), and each application can host several modules.

Characteristics

An application has the following characteristics:
  • A name and ID [1]
    The ID is optional
    [2]
  • A deployment, which defines the jar files which contain the application code[3]
    The deployment is not necessary if the application do not contain any Java module

Note on hosting modules

All Modules of an Application:
  • Are processed in the same JVM
  • Share the same set of data store for each Service[4]
    This means that for modules which are hosted in the same Application, the framework does not have to copy the datas from one Module to another when a Service is invoked

Application configuration


An application XML configuration file contains:
  • The name and identification of the application: these two elements must be unique for all applications in the framework
  • The deployment of the application: this declares the Jar files which contain the Java code for the application[5]
    Note that this part can be omitted if the application does not contain any Java modules
  • The declaration of each module contained in the application

Example

In the following example, the Aircraft application hosts four modules:
  • The InertialNavSystem module computes the current position of the aircraft
  • The FlightManagementSystem module computes the Flight plan and sends the events during the aircraft route on the Flight plan
  • The GuidanceSystem module computes the aircraft trajectory
  • The Cockpit module
      <application name="Aircraft" id="1">
         <deployment>
            <lib url="aircraft.jar" />
         </deployment>
         <modules>
            <module name="InertialNavSystem" id="1" >
      ...
            </module>
            <module name="FlightManagementSystem" id="2" >
      ...
            </module>
            <module name="GuidanceSystem" id="3" >
      ...
            </module>
            <module name="Cockpit" id="4" >
      ...
            </module>
         </modules>
      </application>

Notes

  1. ^ The ID is optional
  2. ^ See identification
  3. ^ The deployment is not necessary if the application do not contain any Java module
  4. ^ This means that for modules which are hosted in the same Application, the framework does not have to copy the datas from one Module to another when a Service is invoked
  5. ^ Note that this part can be omitted if the application does not contain any Java modules

See also


Categories: concepts

Copyright 2017-2020 Dassault Aviation. All Rights Reserved. Documentation and source under the LGPL v3 licence