Generated Classes and Class Hierarchy
The following figure shows the position of the element handler class within the inheritance hierarchy of the classes involved:
Extension Framework |
|
IF_BSP_ELEMENT |
Basic interface that each valid element handler class must implement. The methods and attributes of this interface already define the actual extension framework for BSP applications. |
CL_BSP_ELEMENT |
Basis class with a standard implementation of the IF_BSP_ELEMENT methods for all BSP elements.See also: Basis Class CL_BSP_ELEMENT |
Element-specific classes |
|
(Z)CLG_<EXTENSION>_<ELEMENT> |
This class is automatically generated by the development environment for each new BSP element and is provided as a basis class for the element handler class. It has a 1:1 relationship to a BSP element and already contains a standard implementation for the corresponding element. In contrast to its superclass CL_BSP_ELEMENT, it contains public attributes that correspond to element attributes and, additionally, the standard implementation for the constructor (and, if necessary, for the class constructor as well). |
CL_<EXTENSION>_<ELEMENT> |
The element class, too, has a 1:1 relationship to a BSP element and implements its specific functions. As a rule, it is derived from the CLG class. This is recommended, but not compulsory. Compared to its basis class, the element handler class can be enhanced to include specific methods. In addition, special interface methods can be redefined, depending on the element attributes. |