Entering content frame

This graphic is explained in the accompanying text Cross-Component Programming Locate the document in its SAP Library structure

Web Dynpro components are reusable modules. This allows you to build Web Dynpro applications that consist of different components. From within a component, an interface enables you to use the data and functions of another component. The prerequisite for this is that the second component must be available at runtime in an active version.

Within a distributed development project, it makes sense to create generic components to be used by different developers. For more information, see Working with Component Usages.

In addition, it may be useful to create own components only as suppliers of the data required in other components. Such components are called model components; they only make sense whenever several components must access the same set of application data. Model components are components without graphical elements but with the full controller functionality.

The Web Dynpro framework additionally offers the possibility of defining component interfaces independently of concrete components. These separately defined interfaces can then be used and implemented in an application component. The advantage is that all used components have a – at least in parts – uniform interface. Developers who use such components for their applications can then rely on the existence of particular elements in the component interfaces.

For a better understanding of the use of component-internal and cross-component elements, section The Different Controllers of a Web Dynpro Component once more discusses the different controller interfaces and their naming conventions.



Leaving content frame