Show TOC Start of Content Area

Background documentation Interface Controllers  Locate the document in its SAP Library structure

Interface Controller

One Web Dynpro Component may declare the use of another Web Dynpro Component to form a “Parent-Child” usage relationship. In such cases, the only point of interaction between the parent and child components is the functionality found in the child’s interface controller.

There is a usage declaration arrow pointing from the component controller to a child component. Notice that the arrow joins the child component at the top right-hand corner. This is the location of the child’s interface controller.

At no time does the Web Dynpro Runtime interact with a component’s interface controller. It is only ever used to form a Parent-Child relationship between two Web Dynpro Components.

Note

SAP strongly recommends that no application coding be written directly into the methods of the interface controller. Instead, the public methods of the interface controller should simply delegate their functionality to a method of the same name in the component controller. This will greatly reduce the conversion task required when upgrading to the next release

 

Interface View Controller

The visual interface of a Web Dynpro component is supplied via the Interface View. This behaves much like a UI element in so much that it can be embedded into the view layout of a parent view as a single, reusable entity.

Once the interface view of the child component has been embedded into a view layout belonging to the parent component, the parent component then has programmatic access to the visual interface of the child component through the child’s interface view controller.

 

End of Content Area