Home
User Guide
The information contained in this section applies to IBM WebSphere Commerce Version 7.0.0.9 and Feautre Pack 8. The documentation also applies to all subsequent releases and modifications until otherwise indicated in new editions.
Developing
The topics in the Developing section describe tasks performed by an application developer.
Presentation layer
WebSphere Commerce uses Java Server Pages (JSP) to implement the view layer of the Model-View-Controller (MVC) design pattern. The view layer is in charge of retrieving data from the database through the use of data beans and formatting it to meet the display requirements. The view layers determines whether the request is sent to a browser or streamed out as XML. JSP files present a clean separation between data content and presentation.
Customizing IBM Sales Center
In the IBM Sales Center for WebSphere Commerce there is a set of user interface panels, views and dialogs that contain the most commonly used features. You can add to or configure the user interface to suit your needs, as well as changing the content and format of the data that is passed between the client and the server.
Controls
The layout of the IBM Sales Center dialogs and editors are constructed using configured controls. A configured control is a user interface element that is declared using the controls extension point. The definition of a configured control includes a unique identifier, the type of control, and additional attributes and properties that are specific to the type of control being defined. The control type is used to locate a control factory class that will construct the new configured control. Examples of control types include text, label, requiredLabel, combo, pushButton, checkBox, radioButton, table and composite. The complete list of controls is found in the extension point documentation.
Declaring a control
The layout of the IBM Sales Center dialogs and editors are constructed using configured controls. A configured control is a user interface element that is declared using the controls extension point. The definition of a configured control includes a unique identifier, the type of control, and additional attributes and properties that are specific to the type of control being defined. The control type is used to locate a control factory class that will construct the new configured control. This section explains how to declare a control.

Declaring a control

The layout of the IBM Sales Center dialogs and editors are constructed using configured controls. A configured control is a user interface element that is declared using the controls extension point. The definition of a configured control includes a unique identifier, the type of control, and additional attributes and properties that are specific to the type of control being defined. The control type is used to locate a control factory class that will construct the new configured control. This section explains how to declare a control.

About this task

The definition of a control contains the properties of the control. For example:

<control 
    id="logonUserNameField" 
    type="text" 
    required="true" 
    tooltip="LogonDialog.usernameTooltip" 
    managerType="operatorLogon"> 
<property name="fieldType" value="username"/> 
</control>

Procedure

Create a new plug-in to use for your extensions.
In the plugin.xml, declare the control using the com.ibm.commerce.telesales.widgets.controls extension point.
Declare a composite definition to contain your control. Once a control is declared it must be included in one or more composite definitions before it will appear as part of the user interface.

Results

Note: When a control is constructed, the declared attributes and properties will be passed to the appropriate control factory as determined by the control type. The properties will also be available to the widget manager associated with the use of the control.