on 12-07-2007 4:58 AM
hi,
what is the purpose of interface view controller?
Hi,
The following four controller types can be contained in a Web Dynpro Component (see figure above):
1. Component Controller: Every component contains a single component controller by default. It has no visual interface and can be seen as a components master controller.
2. Custom Controller: A custom controller is an optional controller (0..n) inside a component having no visual interface. It is there for implementing specific application logic concerns (value help listeners, configuration) inside a separate controller and outside the component controller.
3. Window Controller: A window controller implements the presentation logic of its related window (0..n, visual interface). The presentation logic mainly deals with handling or firing navigation events (inbound and outbound plugs, startup and exit plugs, suspend and resume plugs).
A window controller can additionally implement one or many component interface view controllers defined in local or standalone component interface definitions.
4. View Controller: A view controller implements the presentation logic of its related view (0..n, visual interface). The presentation logic of a view mainly deals withs firing navigation events (inbound and outbound plugs) or dynamically modifying view layouts in wdDoModifyView() and handles action events, validates user input or simply delegates method calls to window-, custom- or component controller.
Regards
Ayyapparaj
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
1:Interfaceview controller will be used in InterApplicaion Communicaion and
2:If we want to use a view in one component in another component.
3:Each component will have one InterfaceController and One ComponentInterfaceView
4:To use another component in one component we add the interface controller of Second component as required controller of first component.
5:When communicating among components, First interface controller will be called.
there we'll write our navigations to Component controller of SecondComponent.
6:In SecondCompController we'll define navigations
Regards
LakshmiNarayana
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
Interface View Controller is needed for the following scenario
When you have a component that has some generic functionality and you want it to be accessed by any other component other than the current component then you would need Interface Controller.
Here the component that needs to access the functionality is called Parent. The component whose functionality needs to be accessed is called Child. Now parent accesses child through child's interface controller.
In the child's interface controller you would have some context nodes (not its own) that would then be needed to be mapped to the parents context values ..so as to pass the values to child component and get the resultant values after processing.
I hope you get some idea
Regards
Avinash
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.