Creating Components

Procedure

Create a controller (including classes) in a BSP application.

This controller may belong to an already existing BSP application or it can be located in its own BSP application.

Caution

Note that the basic class of this controller and the top-level controller is class CL_BSP_CONTROLLER2 (see also Creating Top-Level Controllers and Views).
If this controller should always be used as the component controller, then change method DO_REQUEST so that only views can be displayed. If not, DO_REQUEST would look exactly the same as the DO_REQUEST from the top-level controller.
- Overwrite methods DO_HANDLE_DATA, DO_HANDLE_EVENT, and/or DO_FINISH_INPUT. These methods are called by the parent controller only with the form fields for the current controller. All components share parameter GLOBAL_MESSAGES. GLOBAL_MESSAGES is used to handle incorrect input. Parameter GLOBAL_EVENT is set by method DO_HANDLE_EVENT and is used in DO_FINISH_INPUT. The component developers should device how these values should be set. Methods DO_HANDLE_DATA and DO_FINISH_INPUT are called for all active components. DO_HANDLE_EVENT only called by the controller that is responsible for the input event.
- For every attribute that should be passed to this controller, create a public attribute or a method.
Create one or several views.
Activate the views.