Entering content frame

Object documentation Web Dynpro Component Locate the document in its SAP Library structure

Definition

A Web Dynpro component is a reusable entity. It groups together all the separate parts required for an application. A Web Dynpro component can contain any number of windows and views with their related controllers, along with optional additional Web Dynpro components.

 

This graphic is explained in the accompanying text

Use

Each Web Dynpro application refers to one Web Dynpro component, or more precisely, to a plug in the interface view of a window contained in the component. A Web Dynpro component can, however, embed other Web Dynpro components, and correspondingly a Web Dynpro component can be embedded in any other Web Dynpro components. An embedded component can be integrated in one of the windows of the embedded component using inbound and outbound plugs. The embedded component then behaves in the same way as a view.

This graphic is explained in the accompanying text

The inner component does not have to have graphical elements. It can also be available for the functions contained in your component controller or for contexts for the outer components.

The interface of a Web Dynpro component

In addition to the visual part (the interface views of the different windows), the interface of a Web Dynpro component also has a programming part. This consists of two controllers, the interface controller and the configuration controller, which are both visible within the component and externally. The interface controller performs the program side of the exchange of business data. The configuration controller is used to control properties of the component, for example, those related to its underlying behavior. An embedded component can also call an embedded component using these two controllers. A third option for data exchange across several components is cross-component context mapping.

The interface of a Web Dynpro component can also be defined independently without implementation. It is therefore possible to separate the development of the Web Dynpro component and the development of one use of the Web Dynpro component. You can also create multiple interface implementations for one Web Dynpro component. For each interface, the required implementation is not selected until runtime.

 

 

Leaving content frame