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.
Business logic
Name-value pair command framework
The name-value pair framework is the only command framework that existed in releases of WebSphere Commerce Version 6, prior to Feature Pack 3.0.1. This command framework uses name-value pairs as input to the business logic layer, and returns the responses as name-value pairs.
Command types
WebSphere Commerce commands are Java beans that contain the programming logic associated with handling a particular request. Commands perform a specific business process, such as adding a product to the shopping cart, processing an order, updating a customer's address book, or displaying a specific product page.
Data bean commands
A command data bean relies on a command to retrieve its data and is a more lightweight data bean. The command retrieves all attributes for the data bean at once, regardless of whether the JSP page requires them. As a result, for JSP pages that use only a selection of attributes from the data bean, a command data bean may be costly in terms of performance time. While access control can be enforced on a data bean level when using the smart data bean, this is not true for command data bean. Only use command data bean if using a smart data bean is impractical.

Data bean commands

A command data bean relies on a command to retrieve its data and is a more lightweight data bean. The command retrieves all attributes for the data bean at once, regardless of whether the JSP page requires them. As a result, for JSP pages that use only a selection of attributes from the data bean, a command data bean may be costly in terms of performance time. While access control can be enforced on a data bean level when using the smart data bean, this is not true for command data bean. Only use command data bean if using a smart data bean is impractical.

The following diagram illustrates the relationship between the implementation class and interface of a new data bean command with the existing abstract implementation class and interface. The abstract class and interface are both found in the com.ibm.commerce.command package.

Diagram illustrating the relationship between the implementation class and interface of a new data bean command with the existing abstract implementation class and interface: MyDataBeanCmdImpl extends DataBeanCommandImpl, and MyDataBeanCmd extends DataBeanCommand.