Network Deployment (Distributed operating systems), v8.0 > Develop and deploying applications > Develop web applications > Develop web applications > Define an extension for the registry filter

Application extension registry

WAS has enabled the Eclipse extension framework for applications to use. Applications are extensible when they contain a defined extension point and provide the extension processing code for the extensible area of the application.

An application can be plugged in to another extensible application by defining an extension that adheres to what the target extension point requires. The extension point can find the newly added extension dynamically and the new function is seamlessly integrated in the existing application. It works on a cross Java EE module basis. The application extension registry uses the Eclipse plug-in descriptor format and API as the standard extensibility mechanism for WebSphere applications. Developers that build WebSphere application modules can use WAS extensions to implement their functionality to an extensible application, which defines an extension point. This is done through the application extension registry mechanism.

The architecture of extensible Java EE applications follow a modular design to add new functional modules or to replace an existing module, particularly by those outside of its core development team. Each module is a pluggable unit, or plug-in that is either deployed into the portal or removed from the Java EE application using a deployment tool that is based upon standard Java EE and portal web module deployment tooling. A plug-in module describes where it is extensible and what capability it provides to other plug-ins in the plugin.xml file. The plugin.xml manifest file can be created with a simple text editor or in Eclipse's Plug-in Development Environment (PDE), which provides a simplified view of the same underlying XML data.

WAS implementations to the Eclipse model

Some minor differences exist in the WAS implementation of this architecture because of platforms, specifically, Eclipse Workbench or Java 2 Platform, Enterprise Edition (Java EE). The highlights of the WAS implementation include:

Available Eclipse 3.1 interfaces

The following Eclipse 3.1 interfaces are available on WAS:

The following interfaces are recognized and processed the same as in Eclipse:

Application extension registry filtering
Define an extension for the registry filter


Web applications: Resources for learning
plugin.xml file
API documentation


Search Tips   |   Advanced Search