You can import portlet applications that were not developed using Composite Application Framework (CAF). The non-CAF applications are JavaServer Pages (JSP)-based applications, and are referred to as legacy portlets.

To work with legacy portlets in CAF, you must enable the MwS Legacy Portlet Support capability. For more information about enabling support for legacy portlets, see Enabling Legacy Portlet Support.

You can log on to the Software AG TECHcommunity website to download legacy portlet code samples included in webm_CAF_Samples_821.zip. You can use these samples to familiarize yourself with importing legacy portlet applications and manipulating the files before you try the same operations with your own applications. For more information about importing legacy portlets, see Importing Legacy Portlets.

After you import your legacy portlet application, you can view the source artifacts in the UI Development perspective’s Navigator or Project Explorer views. The directory structure of legacy portlets reflects the type of application imported. For example, your project might not have a WebContent node in the legacy portlet application.

You can begin modifying the legacy portlet by double-clicking the portlet.xml file to open the portlet.xml and the wm-portlet.xml files in a text editor. Because of their legacy content, the portlet.xml file cannot be opened with the Portlet Application Configuration Editor.