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.
Management Center framework
The Management Center framework is the foundation for business user tooling. The business objects are defined by the individual components that make up the Management Center. The framework uses those definitions to provide all of the features that you can use to find, create, modify, and delete the defined business objects. If you plan to customize the Management Center, it is important to understand the framework and the components that make up the Management Center.
Customizing the Management Center user interface
Customize the Management Center user interface by adding, changing, or removing elements within the user interface.
Customizing an existing Management Center tool
You can customize the Management Center Catalogs, Marketing, Promotions, Store Management, Catalog Filter and Pricing, and Assets tools to meet your business needs.
Changing validation logic
You can include client-side validation logic for the Management Center. Create validation rules for information that users provide using the user interface. For example, validate that users have entered text, not numbers; that a start date is not later than an end date; or that a mandatory field is not empty).

Changing validation logic

You can include client-side validation logic for the Management Center. Create validation rules for information that users provide using the user interface. For example, validate that users have entered text, not numbers; that a start date is not later than an end date; or that a mandatory field is not empty).

About this task

The Management Center includes two types of client-side validation: at the object level, and at the object property level. There are a number of existing validators (see the classes that extend from lzx/commerce/foundation/restricted/Validator.lzx/wcfValidator). You can also implicitly declare validation rules by using the following attributes of lzx/commerce/foundation/restricted/PropertyDefinition.lzx/wcfPropertyDefinition: maxValue, maximumSize, minValue, required, and type. If the existing validators, or the implicit validators, do not meet your needs, you can write a custom validator.

When an object is modified on the client, client-side validation is invoked and if errors are found, the validator adds the error to the object or to a specific object property. The error messages reported by the validator are displayed in the properties view and if the message is scoped to a specific property, the widgets that display that property are given a visual treatment to indicate that the property is in error. When the widget is given focus, any associated error messages are displayed. Client-side messages are also logged in the Management Center message console.