Modules types

Several types of modules are supported:

• Modules which have a Java implementation. These are the default module types. For detailed information on how to develop and configure a Java module, see the and the Java modules paragraph and the Java modules article
• Module instances which are instances of autodescripted modules
• Python Modules which are implemented in Python
• Groovy Modules which are implemented in Groovy scripts
• C Modules which are implemented in C^[1]
  Or more specifically, as C dlls
• User-defined module types which allow to define your own kind of modules and refer to them in the applications configuration. For example, you could define specific module types to handle Simulink modules, or other kinds of modules linked to any other framework or library
• The unique owner module, which allows to create and control the Framework from a parent application

Consequences on applications

Only applications which contain Java modules need to declare a deployment^[2]

The deployment of an application is the list of Jar files containing the Java code of the modules included in this application

Java modules

Java modules are modules which are implemented in Java. These modules are declared by the top-level module element. For example:

      <module name="FlightManagementSystem" id="1" >
         <implementation path="org.da.aircraft.fms.FMS" >
      ...
         </implementation>
      </module>

Module instances

Module instances are Java modules which are instances of autodescripted modules. They don't have any implementation because they instanciate their associated autodescripted module.

These modules are declared by the top-level module or instance element. For example:

      <application name="theAppli">
         <deployment>
            <lib url="myModule.jar" />
         </deployment>
         <modules>
            <module name="module1"/>
         </modules>
      </application>

or:

      <application name="theAppli">
         <deployment>
            <lib url="myModule.jar" />
         </deployment>
         <modules>
            <instance name="module1" instance="myInstance" />
         </modules>
      </application>

Groovy modules

Groovy modules are modules which are scripted in the Groovy scripting language. These modules do not need a deployment in their parent application because they are scripted.

These modules are declared by the top-level groovyModule element. For example:

      <groovyModule name="FlightManagementSystem" id="1" >
         <groovyImplementation path="fms.groovy" />
      </groovyModule>

Python modules

Python modules are modules which are scripted in Python. These modules do not need a deployment in their parent application because they are scripted.

These modules are declared by the top-level pythonModule element. For example:

      <pythonModule name="FlightManagementSystem" id="1" >
         <pythonImplementation path="fmsModule" inputPort="6000" outputPort="6005" inputSize="1024" outputSize="1024" />
      </pythonModule>

C modules

C modules are modules which are implemented as dlls coded in C.

These modules are declared by the top-level cModule element. For example:

      <cModule name="FlightManagementSystem" id="1" >
         <cImplementation path="fms" />
      </cModule>