When a webdynpro component is very complex containing more than 10-15 views and corresponding context nodes, methods, events, event handlers etc, it might become tedious to handle everything in the same Component Controller.
re-using views/methods/nodes of one WD component in another. Interface Controller would generally come into picture when you are doing component usage of some sort in web dynpro i.e. Interface Controller is created by default when a Web Dynpro component is created. to the other web dynpro components), we make use of Interface controller. Whenever we want views, nodes or methods of a particular web Dynpro component to be available to the outside world( i.e. You can create multiple controllers, but those are called Custom Controllers. Start with the basics, jump right into advanced concepts, or flip straight to workbooks so you can apply your knowledge to real-life exercises. It controls the entire activity of the Web Dynpro Component.Ĭomponent Controller is only one. Writing a Web Dynpro ABAP application may be a job, but it can also be a craftand in this book, you have the tool you need to become a master. It is like a Global or Top Include for a program. The controller formats the model data to be displayed in the view, processes the user entries made by the user, and returns them back to the model.Ĭomponent Controller is the superior of all Controllers. The controller lies between the view and the model. The view is mainly responsible for the displaying the data in the browser i.e. The model forms the interface to the back end system and thus enables the Web Dynpro application access to data. This is based on the Model View Controller paradigm.Įvery Web Dynpro application is structured according to the Model View Controller programming model: The papers are not supposed to be submitted for academic credit. Web Dynpro is the SAP Net Weaver programming model for user interfaces (UIs). All of papers you get at are meant for research purposes only.