Hi,
component controller:
Each Web Dynpro component has at least one global controller, called the componentController. The lifetime of the component controller is determined by the lifetime of the entire
Application. Every Web Dynpro controller has a data storage area known as the context. The component controller is the master controller for a Web Dynpro component. As soon as you declare the existence of a Web Dynpro component, the component controller is automatically created.
__Custom controller:_
Needed for storing context data used across several views. A Custom controller has a longer lifecycle than a View controller. Custom controllers belong to the component and live as long as the component lives in an application.
When should custom controller be used:
Reuse Create a custom controller if you have identified a reuse case for a specific unit of code required by several other controllers within the component.
Task separation To avoid placing too much coding in the component controller (and thereby potentially increasing its initialization time), place coding dedicated to a specific task into a separate custom controller
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.