| | Notes on the Eclipse Plug-in Architecture |
 | | But while the extender plug-in defines the required specific callback objects, and declares their custom implementation classes, the callback objects only come into existence as a result of specific action by the host plug-in (and usually only when they are required for the first time to perform some action on behalf of the extension). |
 | | The configuration of the callback object provided to this method as a parameter would drive the initialization process and would be reflected in the callback object's state by the initialization method. |
 | | For example, when a callback object manages access to a set of resources, it is often possible and preferable to open a managed resource only when it is actually required in a subsequent method call to the callback object. |
| www.eclipse.org /articles/Article-Plug-in-architecture/plugin_architecture.html (10311 words) |