Owner: Free SAP Netweaver Books,Projects And Faq's URL:http://allsapnetweaverlive.blogspot.com Join Date: Sat, 07 Jun 2008 08:52:15 -0500 Rating:0 Site Description: Cross-Component Programming,Dynamic Programming,Integrating Forms,Integration,Integration of ALV,Interview Questions,List Viewer in Web Dynpro Portal Integration,TCodes,Web Dynpro ABAP Site statistics:Click here
Web Dynpro ABAP Component Controller 2008-06-10 00:23:15 Each Web Dynpro component contains exactly one component controller. This controller is automatically created during the component creation and contains a context, events, and methods. Unlike a view controller, the component controller is visible for all views in a component. This means, the controllers of different component views can access context elements or methods of the component controller Read more:Component
Web Dynpro ABAP Context Mapping 2008-06-10 00:22:20 Data stored in the context of the component controller can be used within a view if you link the node of the view context to the corresponding context node of the component controller. This procedure is called “defining a mapping”. For further information, refer to the chapter Data Binding and Mapping
in the architecture manual for Web Dynpro. The following graphic illustrates the principle o Read more:Context
Web Dynpro ABAP Programming Controller Methods 2008-06-10 00:21:47 In general, attributes and methods are used to specify the processes of programs in Web Dynpro applications and to edit the data contained in the context. The previous sections, Action Event Handlers and Cross-Controller Method Call, described simple examples of these program processes. In this section, you find general information on programming using methods of the Web Dynpro framework. In addit Read more:Programming
, Methods
WD_CONTEXT Reference Variable 2008-06-10 00:21:00 WD_CONTEXT The WD_CONTEXT attribute is a reference to the root node of the context of the controller. Regardless of the edited controller, it is always a reference variable of the type IF_WD_CONTEXT_NODE. You can use WD_CONTEXT and the interface methods to edit the content of a context node in your controller method. Example The controller context contains the MY_TABLE_NODE node. You can use Read more:Variable
Reference Variable WD_THIS and Local Controller Interface 2008-06-10 00:20:13 Each controller contains a local interface which can be accessed in the controller. The controller attribute WD_THIS is a reference to this local interface. Depending on the controller, a reference variable is of the following type: · IF_COMPONENTCONTROLLER · IF_ · IF_ · IF_ The methods and attribute of the local controller interfaces can be accessed usi Read more:Variable
, Local
, Interface
Methods of the Local Controller Interface 2008-06-10 00:19:23 All methods that can be changed - that is, methods that can be implemented by the application developer - are listed on the Methods
tab of each controller. When double-clicking the method name, you switch to an ABAP Editor which enables you to implement the source code. In addition to the changeable methods, the local interface of each controller provides several methods which can be used but Read more:Local
, Interface
Hook Methods: Methods Called by the Runtime Web Dynpro ABAP 2008-06-10 00:18:40 Along with the previously mentioned application methods, each local controller interface has a fixed number of methods that can only be called by the runtime. The application developer cannot specify when these methods are called, but can modify the implementation. The time when these methods are called is predefined. For a description, refer to the phase model of Web Dynpro. WDDOINIT and WDDOEXI Read more:Methods
, Runtime
Predefined Methods of the Local Controller Interface Web Dynpro ABAP 2008-06-10 00:17:43 Each controller contains an additional set of methods provided by the runtime. They can be used for developing applications. You cannot change the implementation of the methods – unlike the implementation of all the other controller methods. The content of the method set depends on the controller type and its implementation state. Some of these methods are described in more detail below. Metho Read more:Methods
, Local
, Interface
Events and Event Handlers Web Dynpro ABAP 2008-06-10 00:14:23 You can define events for a component controller to allow cross-controller communication. These events can then be triggered using the predefined method FIRE__EVT. Once the event is triggered, the corresponding event handler is automatically called in another controller by the runtime. A usage of the component controller must be entered in the current controller to handle an event of a component
Web Dynpro ABAP Supply Function 2008-06-10 00:13:02 Each context node of a controller can be assigned a supply function. This supply function is called by the runtime when the data of the context node is used. This is the case when a UI element is to be displayed for the first time with the data of the corresponding context, for example. In general, the supply function is called when one or more elements of a context node are accessed and when Read more:Supply
Free Methods in Application Development Web Dynpro ABAP 2008-06-10 00:12:22 As an application developer, you can create and implement your own methods for each controller. These self-defined methods are typically used to read and edit data. These methods can be called within the controller by other methods that are also implemented by the application developer. Example In the following example, the GET_FLIGHTS method has been implemented to read data from the back end Read more:Methods
, Application
, Development
, Application Development
Web Dynpro ABAP Cross-Controller Method Call 2008-06-10 00:11:23 The Web Dynpro framework enables the application developer to develop source code beyond the controller boundaries. The example of the previous chapter Action Event Handlers is used again to explain the procedure: In the chapter Context Mapping, a cross-view context in the component controller and the required mapping for the example component have already been created. Now, the functions of the Read more:Cross
Web Dynpro ABAP Runtime APIs 2008-06-10 00:10:51 The application developer can use Web Dynpro APIs as a set of interfaces for an efficient design of controller programming. APIs can be accessed in several ways. For a complete list of all classes and interfaces of the framework and the access methods, refer to the reference manual in this documentation. The runtime interfaces offer multiple methods for different programming areas. These include, Read more:Runtime
Web Dynpro ABAP Filling the Context 2008-06-10 00:10:08 The values of the context elements play a crucial role in Web Dynpro for ABAP. Therefore, the filling and changing the context must be thoroughly planned. Depending on when the context is to be filled or updated, you can choose from the following methods. WDDOINIT The method WDDOINIT is the initialization method of the controller. If you know beforehand that the context in your application is Read more:Context
Web Dynpro ABAP Phase Model 2008-06-10 00:08:48 Purpose This section provides information on the data transport during the request processing. The first request is not described as it only involves the reading of the metadata and the initial display of the user interface. At certain points of the phase model, application developers can influence the user interface layout themselves by programming dynamically. Process Flow The following
Web Dynpro ABAP Client Implementation 2008-06-10 00:08:15 The graphic below gives an outline of the concept of the client implementation: Depending on the rendering device selected, the central part of Web Dynpro runtime works together with a specific client implementation. If a browser is selected, the client implementation is server-side rendering (SSR). SSR then takes on the task of communicating with the client device. View elements are kept in Read more:Client
, Implementation
Web Dynpro Window 2008-06-10 00:07:38 The previously described simple application example contained a Web Dynpro component with one view only. In the tutorial of this documentation, the instructions include from the beginning the creation of applications with two views which are connected via navigation. This and the following chapter describe the communication between the different views of a component. Each Web Dynpro component co Read more:Window
Navigation Between Two Views 2008-06-10 00:06:55 All views within a window can be connected to each other using navigation links. When the user calls a Web Dynpro application, the start view is displayed first on the screen. You can trigger a specific action – for example, by clicking a button – which triggers navigation. As a consequence, the previously displayed view disappears from the screen and a second view is displayed. To set up Read more:Navigation
Web Dynpro ABAP Window Plugs: Startup and Exit 2008-06-10 00:06:04 Like Web Dynpro views, each Web Dynpro window has inbound and outbound plugs. Any number of these plugs can be defined as startup or exit plugs. Startup
Plug The startup plug is a special inbound plug. The Startup property, which you can define on the Inbound Plugs
tab page in the window editor, declares for the inbound plug the option to instantiate a component and to start a new application. Read more:Window
Web Dynpro Application 2008-06-10 00:04:56 Another important task of the window is to establish the connection between the structured view group (or at least one individual view) and a URL that can be called by the user. The window is also a unit called by a user using a Web Dynpro application. In general, only one view is displayed on the screen at a time. In the simplest case, the Web Dynpro application calls the view specified as the st Read more:Application
Web Dynpro ABAP URLs and Namespaces 2008-06-10 00:02:05 When you use your own Namespaces (see also Reservation of Namespaces) there are some peculiarities to note with regard to the paths in the ICF Internet service tree and in the MIME repository.When creating your own name spaces follow the rules set out in Defining Naming Conventions.Normally a Web Dynpro application is created in SE80 either in the SAP namespace using its simple name, for example,
Using Parameters to Call a Web Dynpro Application 2008-06-09 23:58:52 UseThe URL parameters of a Web Dynpro application are defined by the main component.The window of a component has one or more inbound plugs, and these may have parameters. If a parameter is defined for an inbound plug, it must be assigned a value at runtime. Usually the URL call will transfer the parameter value to the inbound plug. Alternatively, you can set a default value for this parameter in Read more:Application
Web Dynpro ABAP 2008-06-12 03:25:05 Purpose Web Dynpro for ABAP or Web Dynpro for ABAP (WD4A, WDA) is the SAP standard UI technology for developing Web applications in the ABAP environment. It consists of a runtime environment and a graphical development environment with special Web Dynpro tools that are integrated in the ABAP Workbench (SE80). Web Dynpro offers the following advantages for application developers: ● The us
Web Dynpro Architecture 2008-06-12 03:24:24 DefinitionWeb Dynpro is the SAP NetWeaver programming model for user interfaces (UIs).The Web Dynpro model is based on the Model View Controller paradigm, and has the following features that build on the classic dynpro model:· Clear separation of business logic and display logic· Uniform metamodel for all types of user interfaces· Execution on a number of client platforms.· Extensive platform Read more:Architecture
Web Dynpro Component 2008-06-12 03:22:45 Definition A Web Dynpro component is a reusable entity. It summarizes all components that are required as part of this programming unit for an executable Web Dynpro application. The Web Dynpro component concept offers a number of advantages: ● Structuring of the programming ● Creation of easily manageable application blocks ● Reusability of whole components ● Deco Read more:Component
Web Dynpro Component View 2008-06-12 03:22:18 Definition A view describes the layout and behavior of a rectangular area of a user interface. Use Every Web Dynpro application has at least one view. The layout of a view is made up of different user interface elements, which can be nested in each other. The positioning of interface elements in one view is supported by the supplied layout variants. In addition to the visible part, the layou Read more:Component
Web Dynpro Component View Set 2008-06-12 03:21:48 The concept of view sets is only offered in Web Dynpro for Java. A view set provides a visual frame with predefined subsections into which you can embed your views at design time. Using view sets is particularly advantageous when you design, implement, or display the user interface of a Web Dynpro application: · Structured option to display more than one view in a screen · Read more:Component
Web Dynpro Component Plugs and Navigation Links 2008-06-12 03:21:16 Navigation between different views is enabled by plugs. These can be divided into inbound and outbound plugs. While inbound plugs define the possible starting points of a view, the outbound plugs of a view can be used to call a subsequent view. Plugs
are part of the controller of a view. They are always assigned to exactly one view. Since interface views behave exactly the same as views with re Read more:Component
, Navigation
Recommend Site To A Friend
