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 ID
You might not always want to have the same identifier for an extension definition. There are cases where the choice as to which extension definition should be used needs to be made dynamically. Locale or store are one of the criteria by which you may want to use different name or address user interface elements.

Declaring a dynamic ID

You might not always want to have the same identifier for an extension definition. There are cases where the choice as to which extension definition should be used needs to be made dynamically. Locale or store are one of the criteria by which you may want to use different name or address user interface elements.

Procedure

Create a plug-in to be used for extensions.

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


<extension point="com.ibm.commerce.telesales.dynamicIds">
   <dynamicId
      id="customerNameCompositeDefinition"
     
resolverId="com.ibm.commerce.telesales.ui.localeSensitiveIdResolver"/>
   <dynamicId
      id="customerAddressCompositeDefinition"
     
resolverId="com.ibm.commerce.telesales.ui.localeSensitiveIdResolver"/>
   <dynamicId
      id="customerIdentityCompositeDefinition"
     
resolverId="com.ibm.commerce.telesales.ui.storeTypeSensitiveIdResolver"/>
</extension>

Results

The declaration includes the ID (the resolverID) of a dynamic IdResolver which will be responsible for actually resolving the dynamic ID into the ID of a valid extension declaration. A locale sensitive and a store sensitive dynamic ID resolver are declared in the com.ibm.commerce.telesales.ui plug-in.