Difference between revisions of "Adaptor Hooks"
| Line 1: | Line 1: | ||
| − | + | == Overview == | |
| + | Since Eclipse 3.0 the Framework Adaptor API has been available in the Equinox OSGi Framework. A framework adaptor implementation is called upon by the Equinox OSGi Framework to perform a number of tasks. A framework adaptor may be used to add functionality to the framework. | ||
| + | |||
| + | A single framework adaptor is specified when the framework is launched. By default in Eclipse 3.0 this is set to the EclipseAdaptor. In order to add new functionality in an adaptor in Eclipse 3.0 and 3.1 it is required that the adaptor implementation either re-implement the complete framework adaptor API or extend one of the existing framework adaptor implementations. This makes it impossible for two parties to add new functionality to the framework in separate adaptors at the same time because the Equinox OSGi Framework can only be configured to use one adaptor. | ||
| + | |||
| + | In Eclipse 3.2 a new hookable adaptor has been included that is used by default as the framework adaptor. The framework adaptor API has remained unchanged for the most part in Eclipse 3.2. What has changed is the actual implementation of the adaptor API. A new implementation of the adaptor API is now included which provides hooks that others can implement to provide functionality to the adaptor implementation. | ||
| + | |||
| + | == Hookable Adaptor == | ||
| + | |||
| + | === The Hook Registry === | ||
| + | |||
| + | === Hook Configurators === | ||
| + | |||
| + | === The Base Adaptor === | ||
| + | |||
| + | == Bundle Files == | ||
| + | |||
| + | == Hooks == | ||
| + | |||
| + | === Adaptor Hook === | ||
| + | |||
| + | === Bundle File Factory Hook === | ||
| + | |||
| + | === Bundle File Wrapper Factory Hook === | ||
| + | |||
| + | === Bundle Watcher Hook === | ||
| + | |||
| + | === Class Loading Hook === | ||
| + | |||
| + | === Class Loading Stats Hook === | ||
| + | |||
| + | === Storage Hook === | ||
| + | |||
| + | == Class Loaders == | ||
| + | |||
| + | == Examples == | ||
Revision as of 16:53, 18 April 2006
Overview
Since Eclipse 3.0 the Framework Adaptor API has been available in the Equinox OSGi Framework. A framework adaptor implementation is called upon by the Equinox OSGi Framework to perform a number of tasks. A framework adaptor may be used to add functionality to the framework.
A single framework adaptor is specified when the framework is launched. By default in Eclipse 3.0 this is set to the EclipseAdaptor. In order to add new functionality in an adaptor in Eclipse 3.0 and 3.1 it is required that the adaptor implementation either re-implement the complete framework adaptor API or extend one of the existing framework adaptor implementations. This makes it impossible for two parties to add new functionality to the framework in separate adaptors at the same time because the Equinox OSGi Framework can only be configured to use one adaptor.
In Eclipse 3.2 a new hookable adaptor has been included that is used by default as the framework adaptor. The framework adaptor API has remained unchanged for the most part in Eclipse 3.2. What has changed is the actual implementation of the adaptor API. A new implementation of the adaptor API is now included which provides hooks that others can implement to provide functionality to the adaptor implementation.