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 WebSphere Commerce Accelerator, Organization Administration Console, or Administration Console
The WebSphere Commerce browser-based tools (WebSphere Commerce Accelerator, Organization Administration Console, Administration Console) can be extended or changed. In addition to customizing the tools you can also create a new browser-based tool that uses the same underlying framework. A new tool based on the tools framework is referred to as a WebSphere Commerce tools user interface center.
Tools framework
The tools framework defines user interface elements and functionality used to control and manipulate these elements.
Dynamic lists
Dynamic lists display data from the database, or some other data source whose data and elements are variables. Information describing the format in which to display this data, and actions users can perform on this data, is stored in an XML file.
Using view filters
Instead of specifying a views parameter in the URL of the scroll control command, you can specify each view in the action XML file. To specify a view filter, place a node in the action XML file as follows:

Using view filters

Instead of specifying a views parameter in the URL of the scroll control command, you can specify each view in the action XML file. To specify a view filter, place a node in the action XML file as follows:

About this task


<action ...>
...
...
<view name="sampleList1" actionFile="common.sampleListSC"/>
</action>

the attributes within the code sample have the following meaning:

name
- the key to the resource bundle for the name of the view.
actionFile
- identifies the XML file which defines the view.