What is custom and context controller in webdynpro?

[Former Member]

Hi Gurus,

I am new to webdynpro can you please explain the following,

What is meant by custom controller?

and whst is meant by context controller?

High marks will be rewarded for the useful inputs.

Thanks in Advance,

Dharani

[Former Member · Accepted solution]

Hi,

Go through this.

http://help.sap.com/saphelp_nw04/helpdata/en/c4/862594e85911459301aa71a2b7b6b4/frameset.htm

http://help.sap.com/saphelp_nw04/helpdata/en/e6/986c3e58d0d064e10000000a114084/frameset.htm

Regards, Anilkumar

Message was edited by:

Anilkumar Vippagunta

[Former Member]

Hi ,

A custom controller is a special type of controller of a Web Dynpro application, which the Web Dynpro application developer can create explicitly if required. Like all other controller types, the custom controller contains a context class, which is automatically generated when the custom controller is defined. Furthermore, the custom controller contains imported packages and methods that are then relevant to all classes in a Web Dynpro application. The custom controller is also the part of an application that implements the event handlers and validators that react to actions.

You can define more than one custom controller for a Web Dynpro application. Before starting the application, you use a reference to specify which custom controller is to be valid at runtime. The lifetime of a custom controller is linked to the lifetime of the entire Web Dynpro application.

Cpmponent 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.

This controller can be thought of as being hierarchically superior to all other controllers in the component. Consequently, the lifespan of the component is always equal to the lifespan of the component controller.

When the Web Dynpro Runtime receives the URL of a Web Dynpro Application, the component controller of the root component is instantiated. Here is an example of where the Web Dynpro Runtime automatically interacts with coding written by the Web Dynpro developer.

Since the component controller has no visual interface, it is incapable of directly presenting any information to the user. This task however, is of no concern to the component controller. The component controller should contain only the coding necessary to control the interaction of all the other controllers and child component instances within the component. You should regard the component controller as the central point of control for the behavior of the Web Dynpro Component.

And go thru these links

Thanks

Lohi.

Message was edited by:

Lohitha M

[roberto_tagliento]

http://help.sap.com/saphelp_erp2005/helpdata/en/43/ec197a15444c60e10000000a155369/frameset.htm

and first of all this

sorry but...