Show TOC Start of Content Area

Background documentation Contexts  Locate the document in its SAP Library structure

Every Web Dynpro controller has exactly one hierarchical data storage area known as its controller context.

This graphic is explained in the accompanying text

Before any data can be stored in the context at runtime, metadata must first be created that describes the runtime data. The creation of context metadata is often done at design time, but can also be done dynamically at runtime.

Note

The data held in the context exists only for the lifespan of the controller. Once the controller instance has been terminated, all data held within its context is lost.

Data Visibility

Although each Web Dynpro controller cannot function in isolation from the Web Dynpro component within which it has been defined, each controller is nonetheless an independent program. Consequently, controllers do not normally have access to each other’s data or functionality.

In order for two controllers to be able to share data with each other, one controller must expose its context through its public interface.

More Information

      Context Mapping

      Creating Context Trees Manually  

 

End of Content Area