E-mail
|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Changes (13)
View Page History
...
{section} h2. Mechanism starting a Petals ESB node
When starting a Petals ESB node, the Fractal composite '*{{Petals}}*' is initialized and started. It is composed of following Fractal components or composites:
* {{ConfigurationServiceImpl}}, that manages the configuration of the Petals ESB node,
* {{PreExtensionsManager}}, that manages the pre-extensions to load before all internal components
* {{PetalsCompositeControllerImpl}}, that manages the startup of other Fractal components according to the current configuration.
{{PetalsCompositeControllerImpl}} starts, in order:
{{PetalsCompositeControllerImpl}} starts, in order:
# the extensions that must be loaded first,
# internal components
# the extensions that must be loaded last.
# the extensions that must be loaded last.
The Fractal composition is controlled by the Fractal component 'PetalsCompositeControllerImpl'.
h2. Mechanism for additional internal component pre-extensions
When Petals ESB starts, the classloader is scanned by the pre-extension manager ({{PreExtensionManagerImpl}}, a component of the composite {{PreExtensionsManager}}) to search all pre-extensions. When one is found, it is instantiated and started. An extension A pre-extension is found when a Java class implementing the interface {{org.ow2.petals.microkernel.api.extension.PetalsPreExtensionController}} is found.
When a {{PetalsExtensionController}} is found, the extension manager ask the extension to create its own Fractal composite/component. Next if the extension is a typed extension (see below), the extension manager registers the new extension to the its associated extension manager.
When a {{PetalsPreExtensionController}} is found, the extension manager ask the extension to create its own Fractal composite/component, bounds it and starts it.
An extension can be typed to have more interaction with other components. Only one sub-type is supported nowadays:
* {{InstallationExtension}}: a such extension interacts with installation and deployment subcomponent, so you install or deploy wiith standard ways and uninstall or undeploy with your extension.
* {{InstallationExtension}}: a such extension interacts with installation and deployment subcomponent, so you install or deploy wiith standard ways and uninstall or undeploy with your extension.
All pre-extensions are unregistered, stopped and freed when the {{PreExtensionManagerImpl}} is stopped.
All extensions are unregistered, stopped and freed when the {{ExtensionManager}} is stopped.
h2. Mechanism for mutable implementation
When {{PetalsCompositeControllerImpl}} starts, for each internal component providing mutable implementation, the classloader is scanned to search the mutable implementation. When one is found, it is instantiated, bound with other internal components and started.
When {{PetalsCompositeControllerImpl}} starts, for each internal component providing mutable implementation, the classloader is scanned to search the mutable implementation. When one is found, it is instantiated, bound with other internal components and started.
A mutable implementation of an internal component is found when a Java class implementing the interface of the internal component is found.
h2. Mechanism for post-extensions
When Petals ESB starts, the classloader is scanned by the post-extension manager ({{PostExtensionManagerImpl}}) to search all post-extensions. When one is found, it is instantiated and started. A post-extension is found when a Java class implementing the interface {{org.ow2.petals.microkernel.api.extension.PetalsPostExtensionController}} is found.
When a {{PetalsPostExtensionController}} is found, the extension manager ask the extension to create its own Fractal composite/component. Next if the extension is a typed extension (see below), the extension manager registers the new extension to the its associated extension manager.
An extension can be typed to have more interaction with other components. Only one sub-type is supported nowadays:
* {{InstallationExtension}}: a such extension interacts with installation and deployment subcomponent, so you install or deploy with standard ways and uninstall or undeploy with your extension.
All post-extensions are unregistered, stopped and freed when the {{PostExtensionManagerImpl}} is stopped.