on 09-09-2008 12:46 PM
hi experts
what is the mean and purpose of component controller, custom controller and interface controllers?
in which situation which controller is used?
how to implement these controllers?
thanks
ramu.
Hello Ram,
Component Controller :-
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. You cannot have a Web Dynpro Component without a component controller. What ever u define in this controller can u used globally any where with in that component.
Custom Controller :-
This custom controller is similar to component controller.
Custom controllers should be created only when their presence will simplify the overall structure of the component. The existence of custom controllers is controlled entirely by the Web Dynpro developer at design time.The principles to follow for deciding when a custom controller is needed are:
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.
Interface controller:
This interface controller is used as an interface between the two components. Using this interface controller u can map values of one component to another component.
Regards,
Arun
Edited by: Arunagiri A on Sep 9, 2008 3:45 PM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi,
View Controller:
View controllers belong to views and live exactly as long as the views are displayed.
component controller:
Special (default) custom controller which allways exists. Custom controllers have to be named and declared.
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.
Interface Controller:
Programming interface allowing the embedding code to interact with a component. The component interface comprises a visual (interface views) and a programmatic (controller and context) part.
watch this thread for more information:
http://help.sap.com/saphelp_nw70/helpdata/EN/4c/40ba420db1cc66e10000000a1550b0/frameset.htm
regards
vineela
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ramu,
Watch these Links
http://help.sap.com/saphelp_erp2005/helpdata/en/b9/b82c4142aef623e10000000a155106/content.htm
With Regards,
Roop Kumar.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi ram,
Check these links, you will get an idea...
http://help.sap.com/saphelp_erp2005/helpdata/en/b9/b82c4142aef623e10000000a155106/content.htm
PradeeP
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
refer this link,
http://help.sap.com/saphelp_nw70/helpdata/EN/4c/40ba420db1cc66e10000000a1550b0/frameset.htm
Regards,
ramesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.