difference betweencomponent controller,Custom controller&Interfacecontrolle

[Former Member]

Hi all

what is the main difference b/w component controller , custom controller & interface controller.

i want to know the difference of these three in the real time environment.

if anybody explains me with any simple example then it is great help to me....

Thanks

Suresh babu.

[Former Member · Accepted solution]

Hi Suresh ,

Hi,

Component Controller and Custom Controller are more or less the same. Both are related to a particular component in the webdynpro application you create.

Component Controller:-

For each component of yours there will be a component controller, were in you can define context variables and methods, events etc.. This usefull while using models.

Simple example where we can see this is, when you create global context variable in this controller and map this variable to the view controller context variable of different view, which enables you to pass the value of the variable from one view to another.

Custome Controller:-

They also have the same the function but as the name suggest there function can be customised. That is we can have more than one custom controller for a component. This is usefull when we need to create seperate execute methods for inputs from model import( Both webservice and rfc call).So you can seperate each other. Example is there in the more sample codes and application section.

Interface Controller:

There is only one interface controller for a component. It is mainly used when we need to communicate between two components.There is sample application for communication between two components in the sample codes and application section.

I think this is enough to get an idea on the difference between each of controllers.

ref

Koti Reddy

[Former Member]

Hi,

You have many documents in SDN you can go through them, you will be having indepth knowledge on them. In brief, the following is the definitions

Custom controllers

Custom controllers are used to encapsulate units of functionality that are shared by several controllers

and require no direct user interaction. Such controllers therefore have no visual interface.

For instance, a custom controller could be used, when a BAPI is called, and the information returned

requires some sort of intermediate processing before it can be displayed.

Before implementing a custom controller, consider carefully whether its presence will simplify or

complicate the overall architecture of your application. Custom controllers should only be added in

situations that will optimize or simplify the architecture of your application.

component controller

The component controller is a that is automatically created when a

component is created. It is this controller that drives the functionality of the entire component.

The interface(s) that this single component presents to either the Web Dynpro Framework or the

embedding controller are defined as . There is a one to one relationship between

a component interface view and a component window.

Interface Controller

This controller is also a special custom controller. This is the only custom controller visible to other

components.

Regards

Raghu

[Former Member]

Hi Suresh,

Wb Dynpro applications are made up of Web Dynpro Components & Models. Web Dynpro Components are collection of views and controllers.By default Web Dynpro Components has the following controllers Component Interface View Controller,Component Interface Controller,Component Controller all oter are optional.

Interface Controllers:An Interface Controller is the only part of a component that is accessible to other components If any data, methods or events need to be exposed to other Components they must be exposed in Components Interface Controller.

Component Controller & Custom Controller:For each component a Component Controller is defined by default.

Component Controller should act as a processing layer b/w model and views and take no part in how the data is visualised.

Custom Controllers are essentially same as Component Controller but u can create them when needed.you can create Custom Controller whenever u want to encapsulate seperate logic.u can have multiple Custom Controllers.

Regards,

Tilak.

[Former Member]

Hi,

Controllers Conecpt mainly deals with the separation of the code/logic and the layout in the MVC pattern. Actual business logic is handled in these controllers.

Please find the link for the usage and impoertance of each controller-

http://help.sap.com/saphelp_nw70/helpdata/EN/b9/b82c4142aef623e10000000a155106/content.htm

[vivekananthan_sellavel]

hi suresh babu;

1.component controller defaultly created by studio where as custom controller is created by developer.

2.only one component controller is creater for an application

N number custom controller can be created by user. based on the requirement

Regards

Vivekanananthan.S