Webdynpro Controllers for ABAP, Component,View,Window,Custom Controllers. Controllers contain the source code of a Web Dynpro application, they hold the context data and care for event handling and navigation. Any programming of flow logic requires the knowledge of how controllers are defined and what kind of entities they offer. This post consist of brief information on Controller in Webdynpro for ABAP Programming for beginners who are looking for information on SAP Web Dynpro ABAP. Read more to refer this post on Webdynpro ABAP Controllers.
SAP Webdynpro Controllers for ABAP Component View Window Custom
Webdynpro Controllers for ABAP, Component,View,Window,Custom Controllers. Controllers contain the source code of a Web Dynpro application, they hold the context data and care for event handling and navigation. Any programming of flow logic requires the knowledge of how controllers are defined and what kind of entities they offer. This post gives a brief introduction to ABAP Web Dynpro controllers.
Special attention will be given to the differences between the different controller types that can exist in a Web Dynpro component.
Controller Types in ABAP Webdynpro
There are four types of controllers in an ABAP Web Dynpro component. These
different controller types differ in the entities they are composed of:
Component controller
There is only one component controller per WebDynpro component. This is a global controller, visible to all other controllers.
The component controller drives the functionality of the entire component. This controller has no visual interface.
The lifetime of the component controller equals the lifetime of the component.
When starting a Web Dynpro application, the component controller is instantiated by the Web Dynpro runtime.
View Controller
View controllers,Each view consists of the layout part and exactly one view controller.
This controller cares for view-specific flow logic, like checking user input and handling user actions.
The instantiation of a view controller is delayed until the first method of the controller is called.
The lifetime of a view controller can be controlled by the views properties:
Window Controller
Window controllers,Each window has exactly one window controller.
This controller can be used to care for the data passed via the inbound plugs when being reused as a child controller.
Methods of this controller can be called from the inbound plug methods of the window.
The instantiation of a window controller is delayed until the first method of this controller is called.
This is done by starting a Web Dynpro application or by embedding the related interface view in the parent component's window.
Window controller instances can not be deleted explicitly.
Custom Controller
Custom controllers,Custom controllers are optional.
They have to be defined at design time and can be used to encapsulate sub-functions of the component controller.
Multiple custom controllers can be defined in a component.
Custom controllers are instantiated automatically by the Web Dynpro framework and the instantiation order is undefined; therefore, the coding in a custom controller should make no assumptions about the existence of any other custom controller.
The instantiation of a custom controller is delayed until the first method of the controller is called. Custom controller instances can not be deleted explicitly.
"You found the information helpful and want to say thanks? Your donation is enough to inspire us to do more. Thanks a bunch!"
Posted in: 
0 comments:
Post a Comment
Note: Only a member of this blog may post a comment.