Working Dynamically with Component Usages 

The chapter on cross-component programming explained the principles of how to use components and interfaces. In that case, the involved components have been known at design time and all navigations or method usages could be determined statically. In practice, however, in many cases this information is not available at design time so that the usage must be created dynamically and can be generated only at runtime, after the name of the desired component has been passed. Consequently, all subsequent steps (such as Embedding an Interface View or Registration onto an Event of a Used Component etc.) must be programmed dynamically to be generated at runtime. The documents below give an overview on frequently used substeps within a dynamic component usage.

Your system contains an example application in which you can, among others, repeat the steps described here.

 The application WDR_TEST_DYNAMIC is designed to visualize the interface views of different components as tab strips. All used components implement the component interface WDR_TEST_DYNAMIC_CI. At the interface controller of this component interface, the method MY_METHOD and the event DATA_SELECTED are defined. The component interface also contains the interface view W0.