Overview

The JavaBeans-based client toolkit provided with ContentConnect allowed you to create your own custom applications using the graphical user interface JavaBeans (visual beans) and the non-visual connection and viewer beans. EIP provides a similar JavaBean toolkit. The beans in EIP are functionally equivalent to the beans provided in ContentConnect .

This document describes the similarities and differences between the visual beans (non-visual beans are also discussed though) in ContentConnect and EIP . Using the sample client application shipped with ContentConnect this document also shows how to migrate a client application created with the ContentConnect beans to a client application using the EIP beans.

Before reading this document, review the documentation ContentConnect Building a Client. This document provides information about the ContentConnect JavaBean components. With the ContentConnect toolkit installed, you can access the documentation from the taskbar by selecting:
Start - Programs - IBM ContentConnect - Toolkit Documentation - ContentConnect Building a Client

In addition, refer to the OO and Internet Application Programming Guide section, "Understanding and using JavaBeans". This document provides information about the EIP JavaBean components. 

Understanding visual bean name changes

Visual beans names have changed between ContentConnect and EIP. In general: The following table shows the specific name differences.
ContentConnect bean EIP bean Description
EJMSearchTemplateListTabs CMBSearchTemplateList Provides an interface for displaying search templates
EJMSearchTemplateViewer CMBSearchTemplateViewer Provides an interface for displaying a search criterion
EJMResultsViewer CMBSearchResultsViewer Provides an interface for displaying search results
EJMFolderViewer CMBFolderViewer Displays the contents of one or more folders in a Windows Explorer -style presentation 
EJMPopup default pop-up (1) Creates a pop-up menu
EJMLogon CMBLogonPanel Displays a window for logging on to the federated servers. The window allows users to change their passwords. 
EJMItemUpdateHandler CMBItemAttributesEditor Displays a window with which users can update index class and indexing attributes for an item
Note: 
(1)You can suppress the default pop-up menu by setting a property in the CMBSearchResultsViewer and CMBFolderViewer beans. In this way, you can replace the default pop-up with a custom pop-up menu. 

Understanding visual beans event changes

You can use the events provided by the ContentConnect toolkit for notification when the state of a bean changes. As shown in the following table, the events emitted for certain actions have changed between ContentConnect and EIP .

EIP includes many new events that provide greater flexibility when creating a client application. For more information about the new events provided in EIP , refer to the OO and Internet Application Programming Guide section, "Understanding and using JavaBeans - visual beans".
ContentConnect event EIP event Action emitting event
EJMTemplateChangeEvent CMBTemplateSelectedEvent Select a template
EJMTItemsSelectedEvent CMBViewDocumentEvent Double-click an item in the search results viewer
EJMPopupEvent CMBItemsPopupEvent (1) Right click a document in the search results viewer or folder viewer
Note: 
(1) In EIP you can create a custom pop-up menu that listens for the CMBFolderPopupEvent and CMBItemPopupEvent events. These events are emitted when a user right clicks a folder in the tree pane or a document in a details pane, respectively. If you use a custom pop-up menu, you must set to false the property DefaultPopupEnabled in the search results viewer bean and the folder viewer bean. 

Understanding non-visual bean name changes

The visual beans for ContentConnect and EIP are dependent upon two non-visual beans:

Converting the client sample application

This section describes how the client sample application (ClientDemo.java) shipped with ContentConnect was converted to become the client sample application shipped with EIP (ClientSampleApp.java).

ClientDemo.java is in the ejmroot\samples directory. ClientSampleApp.java is in the cmbroot\capp\samples directory. To follow the example in this section you might want to edit or print both ClientDemo.java and ClientSampleApp.java.

The following list summarizes the changes: