Plug-in extension components implement interfaces defined by the plug-in API.
The plug-in framework calls methods on these interfaces. Services provided by the framework to the plug-in implementation are passed to the extension components via a context object.
Fundamental extension interfaces: imc3
The fundamental extension components of a plug-in, the editor, generation and collection components, are implementations of corresponding interfaces. The recommended practice is to implement each as a separate class.
Fundamental framework interfaces: imc3
The framework interfaces are implemented by the MashupHub plug-in framework to support plug-in extension components. The plug-in framework API is accessed through a set of extension point-specific context objects and a metadata object.
Framework security interfaces: imc3
Use the Identity Service API to extend the identity management capabilities of plug-ins beyond what is supported in WebSphere®. You can use the Identity Service System Programming Interface (SPI) to write your own Security Token Service (STS) implementation class to use with the Identity Service API. The WS-Trust API provides a way to issue WS-Trust requests when you develop Identity Service STS implementations.
Parent topic: Plugin API: imc3