PackagingAdded by IBM on October 4, 2010 | Version 1 (Original)
|Client applications and Target Features are packaged as features, each of which consists of one or more components. The client platform cannot directly run Java™ EE packaging artifacts such as EAR and WAR files.
Client applications and Target Features are packaged as features, each of which consists of one or more components. The client platform cannot directly run Java EE packaging artifacts such as EAR and WAR files.
The Eclipse framework, and therefore the client platform, is organized around a plug-in and extension point model. The framework provides a core set of components. Additional components are provided in a directory or JAR file organized in a specific structure, and implement instantiations of the various extension points. The framework reads the component declarative information, and incorporates the components into the correct locations in the framework.
A component may not always provide a complete implementation. In some cases, fragments
may be used to complete or extend a component.
On disk, an Eclipse-based product is structured as a collection of components and fragments. Each component or fragment contains the code that provides some of the product's functionality. The code and other files for a component or fragment are installed on the local computer, and get activated automatically as required. A product's components are grouped together into features
. A feature is the smallest unit of separately downloadable and installable functionality
Parent topic: Application design considerations: XPD621