Introduction

Petals ESB implements a plug-in mechanism to be able to extend it with new features. Some optional features of Petals ESB are developed as extensions: Petals Autoloader, Petals Artifact Repository, Petals WS-API.

Two extension natures are supported:

• Mutable implementation of required internal component: the implementation of an internal required component can be changed to be adapted to the use cases, for example: remote transporter, in-memory repository, ...
• Additional internal component to add new features to Petals ESB. A such additional internal component is not required and not used by other internal components.

The mechanism

When Petals ESB starts, the classloader is scanned to search all extensions. When one is found, it is instantiated and started. An extension is found when a Java class implementing the interface org.ow2.petals.microkernel.api.extension.PetalsExtensionController is found.