If new data is to be available for the Web Dynpro application, you must define value nodes and value attributes. These affect the behavior of the custom controller context at runtime. Value nodes do not store data themselves, unlike model nodes, which refer to external model objects that store the data. You get a node collection that consists of node elements. The cardinality provides information about the number of possible node elements in a node collection.
You have already created a component as well as the operating controller unit. For central data flow tasks, this is generally the custom controller.
To define value nodes and value attributes for the context, proceed as described under “Context Structure”.
The subclass
contains set and get methods for the attributes. You can create an instance
for the subclass and fill it with data. The binding method is then called to
add the node instance to the context. In the application entity that contains
the event handlers, the binding routine can be accessed with:
context.bind<myValueNode>(…) |
At runtime, the framework calls the set and get methods to read or change the data in the context.
See also: “Programming Controller Code”.