Tuesday, July 12
SAP Web Dynpro Component Concept
A Web Dynpro component can be reused in other web dynpro components. It is a collection of all entities required to create an executable Web Dynpro application.Web Dynpro component has a number of advantages:
Programming becomes structured
Application blocks become manageable
Reusability
Entire software projects can be worked upon by various developers in various time zones.
The Web Dynpro component mainly consists of windows and views and their corresponding controllers. Web Dynpro components can be used within web dynpro components.
It is mandatory to create a Web Dynpro Component if you want to create a web dynpro application. The application contains views and windows and their corresponding controllers. All these things can come into existence only when a component is in place. To a Component, a Component can talk. Also to a Component, a user can talk. These two type of communications are possible thourgh Component Interfaces.
So each component has its interface. Data and Functionality of a component can be accessed through this Interface.
For this communication to take place, components need to be enbedded. For example, In a Component called TravelComp, there is a method called Speed(). If you another Component called MainComp wants t ouse the method Speed(), It has to enbed the TravelComp first. Then Through the Interface of the TravelComp, MainComp can call the method called Speed() Provided that method is Public in TravelComp.
Lifetime of a Web Dynpro Component
When you create a Web Dynpro Application, you need to create the web dynpro component first. Web Dynpro Component will beinstantiated on the launch of the web dynpro application. This is the beginning of the lifetime of a web dynpro component. The first method executed when a web dynpro component gets instantiated is wdDoInit(). The lifetime of a web dynpro Component is ended when the application itself is shut down or logged off. For embedded Components, the case is a little different. Embedded components are not instantiated unless they are required. So if you call a method present in a embedded component, they will get instantiated otherwise they won't. It is also possible to control the lifetime of a embedded component. This can be done programatically using a Java API. You can create or destry the embedded component instance as and when required.
Related Posts :
SAP Web Dynpro Component Concept
SAP's Standard UI technology Web Dynpro for ABAP
SAP Web Dynpro Terminology
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment
You are welcome to express your views here...