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.
Dynamic IDs
In some cases, it may not be possible to statically declare the identifier for an extension definition. There are cases where the choice of which extension definition to use needs to be made at run time. For example, if the layout of a composite depends on the current locale, then you cannot use the same extension declaration for every locale. The locale must be checked and the composite definition declaration must be chosen. To handle this, the system configurator allows dynamic identifier resolution.
Declaring a dynamic IdResolver
In some cases, it may not be possible to statically declare the identifier for an extension definition. There are cases where the choice of which extension definition to use needs to be made at run time. This section explains how to declare a dynamic IdResolver.

Declaring a dynamic IdResolver

In some cases, it may not be possible to statically declare the identifier for an extension definition. There are cases where the choice of which extension definition to use needs to be made at run time. This section explains how to declare a dynamic IdResolver.

About this task

The dynamic IdResolver will be responsible for resolving a dynamic ID into the ID of a valid extension declaration.

Procedure

Create a new plug-in to contain your extensions.

In the plugin.xml file of your new plugin, declare the dynamic IdResolver using the com.ibm.commerce.telesales.dynamicIdResolvers extension point. For example:


<extension
point="com.ibm.commerce.telesales.dynamicIdResolvers">
   <dynamicIdResolver
      id="storeTypeSensitiveIdResolver"
     
class="com.ibm.commerce.telesales.ui.resolvers.StoreTypeSensitiveIdResolver"/>
   <dynamicIdResolver
      id="localeSensitiveIdResolver"
     
class="com.ibm.commerce.telesales.ui.resolvers.LocaleSensitiveIdResolver"/>
</extension>

Results

Note: A locale sensitive and a store sensitive dynamic ID resolver are declared in the com.ibm.commerce.telesales.ui plug-in.