￿Apache Tomcat, which can be installed only locally and supports testing of Web applications.

4.2.11Plug-in development tools

The WebSphere Studio family (except for Site Developer Advanced) include the PDE (Plug-in Development Environment) which is designed to help you develop platform plug-ins while working inside the platform workbench, and it provides a set of platform extension contributions (views, editors, perspectives, etc.) that collectively streamline the process of developing plug-ins inside the workbench. The PDE is not a separate tool, but it is a one of perspectives. PDE blends with the platform and offers its capabilities through a new perspective.

The following project types are supported:

￿Plug-in project

WebSphere Studio Application Developer is based on the concept of plug-ins, which have a clearly defined structure and specification. This project supports creating, testing , and deploying a plug-in in the PDE.

￿Fragment project

A plug-in fragment is used to provide additional plug-in functionality to an existing plug-in after it has been installed. Fragments are ideal for shipping features like language or maintenance packs, which typically trail the initial products by a few months.

￿Plug-in component

PDE attaches a special component nature to plug-in and fragment projects to differentiate them from other project types. The project must have a specific folder structure and a component manifest. The project must be set up with references to all of the plug-in and fragment projects, which will be packaged into the component.

78 The XML Files: Development of XML/XSL Applications Using WebSphere Studio

Page 94
Image 94
IBM Version 5 manual Plug-in development tools, Plug-in project, Fragment project, Plug-in component