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 marketing
Working with Product Advisor
Java beans in Product Advisor
Product Advisor provides several beans for you to use when creating your display pages. These include static data beans, which are responsible for retrieving data from the server, such as merchant or customer information. Static data beans are used when you plan to render the retrieved data using very little formatting on the page, generally as straight text. Data beans are rendered using scriptlets.
Widget beans
Widget beans render data for Product Advisor from dynamic data beans. For every dynamic data bean, there is a corresponding widget bean that provides the dynamic HTML. The dataBeanName parameter is required for all widget beans. This parameter is required to link a widget bean to the correct dynamic data bean.

Deprecated feature

Widget beans

Widget beans render data for Product Advisor from dynamic data beans. For every dynamic data bean, there is a corresponding widget bean that provides the dynamic HTML. The dataBeanName parameter is required for all widget beans. This parameter is required to link a widget bean to the correct dynamic data bean.

Product Advisor uses the following widget beans: