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.
Views
Several default views are available for customization within the IBM Sales Center client. These views are defined in the com.ibm.commerce.telesales.ui.impl plug-in using the base Eclipse product org.eclipse.ui.views extension point. For more information about views, refer to the Eclipse platform documentation.
Extending a view
Several default views are available for customization within the IBM Sales Center client. This section explains how to extend a view.

Extending a view

Several default views are available for customization within the IBM Sales Center client. This section explains how to extend a view.

Procedure

Subclass the view using the API documentation for the view implementation class as a reference. For example:


ExtendedStoresView.java

package extensions;

import com.ibm.commerce.telesales.ui.impl.views.stores.StoresView;

public class ExtendedStoresView extends StoresView {
        
        public ExtendedStoresView() {
                // indicate in console that the extension is being
used
                System.out.println("ExtendedStoresView");
        }
}

Define the new view using the org.eclipse.ui.view extension point. For example, in the extensions plug-in manifest file:


<?xml version="1.0" encoding="UTF-8"?>
<?eclipse version="3.0"?>
<plugin>

   <extension
point="com.ibm.commerce.telesales.configurator">
      <configurator path="config"/>
   </extension>
   <extension point="org.eclipse.ui.views">
      <view name="Stores"
            category="com.ibm.commerce.telesales.ui.impl"
            
            id="extensions.storeview">
      </view>
   </extension>
</plugin>

Use the System Configurator Extension Point to indicate that the IBM Sales Center perspective will use the new view instead of the default IBM Sales Center view. For example:
```
com.ibm.commerce.telesales.ui.storeview=extensions.storeview
```