Master modules

Master modules are modules which have specific rights to change the states of other modules during runtime:

• Attach or detach a module as a provider
• Enabling or disabling a module

Attaching or detaching a provider

A master module can attach or detach a module as a provider during runtime.

For example:

      <applications>
         <application name="application">
            <modules>
               <module name="masterPublisher" >
                  <interfaces>
                     <subscribe service="published" attach="attach" isMaster="true" />
                  </interfaces>
               </module>
               <module name="publisher2"  >
                  <interfaces>
                     <subscribe service="published" attach="attach" />
                  </interfaces>
               </module>
               <module name="subscriber" >
                  <interfaces>
                     <subscribe service="publish" />
                  </interfaces>
               </module>
            </modules>
         </application>
      </applications>

The methods to attach and detach a module to / from a Service are:

• Attach itself: ServiceInstance.attach()
• Attach any module: ServiceInstance.attach(ModuleIDKey) and ServiceInstance.attach(ModuleKey)
• Detach itself: ServiceInstance.detach()
• Detach any module: ServiceInstance.detach(ModuleIDKey) and ServiceInstance.detach(ModuleKey)

Enabling or disabling a module

By default all modules declared in the applications configuration are enabled, however it is possible to disable explicitly a module in the module configuration.

A master module is able to change the enable state of a module during runtime. The methods are:

• Module.setEnabled(ModuleKey, boolean)
• and Module.setEnabled(ModuleIDKey, boolean)