![]() ![]() ![]() However, in Web Dynpro this concept has been changed so that there are now – broadly speaking – two categories of controller the differences between which will be described later in this document. In the original MVC paradigm, a controller was responsible for managing the interaction of view and model, formatting the model data to be displayed in a view, and calculating which view was to be displayed next. It represents input and output data in the interface e.g. This mainly handles graphical and textual output at the interface. ![]() In other words, the Web Dynpro application doesn’t need to concern with the specific communication technology required to interact with the back end system.Ī view is used to define a client neutral visualization of the business data. Its purpose is to act as a proxy that detaches the Web Dynpro application from the data and functionality found in the remote system. Even when the pages change the data in the previous page still remains.Īs an initial starting point, the well established Model View Controller (MVC) design paradigm was used to provide the architectural foundation for Web Dynpro.Ī model object encapsulates the interface to some back end system. Automatic data transfer using context binding.ĥ. Separation of layout and business data.Ĥ. All use of ICT resources and ICT data is subject to monitoring and investigation as set forth in ST/SGB/2004/15. Web Dynpro for ABAP is the SAP standard UI technology for developing Web applications in the ABAP environment.Ģ. Technology ('ICT') resources and ICT data is consistent with their obligations as staff members or such other obligations as may apply to them. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |