hi Mahesh,
This might be useful for u..
Web Dynpro for Java
The following documentation on Web Dynpro technology is part of the Development Manual and describes the concepts and procedures required by application developers for working with Web Dynpro.
Information on Web Dynpro technology as part of the IT scenario Application Development, Configuration, and Adaptation is available in the variant description Developing Java Applications with Web Dynpro. Here you will find a list of the processes and process steps of the Web Dynpro Java variant.
Web Dynpro is used to design user interfaces for Java and ABAP applications. The current description concentrates on Web Dynpro for Java; the documentation for user interface development on the ABAP platform is available under Web Dynpro for ABAP.
Purpose
Web Dynpro is a client-independent programming model of the SAP NetWeaver technology platform for developing user interfaces for professional business applications. It is based on the model view controller paradim which ensures that the business logic is separated from the presentation logic. This architecture is visible in the Web Dynpro perspective of the SAP NetWeaver Developer Studio (NWDS).
Web Dynpro helps you with the development of Web applications by:
• Ensuring platform-independence with the meta model approach
• Minimizing the implementation effort through declarative programming
• Supporting a structured design process by applying the model view controller paradigm
• Providing reuse and better maintainability by using components
• Providing graphical support with tools in the Web Dynpro perspective
• Providing the SAP NetWeaver Java Development Infrastructure (NWDI) which supports team work with different services such as source code versioning and the Central Build Service.
Meta Model and Declarative Programming
When you program an applicaton using the Web Dynpro tools, the system generates a platform-independent meta model. From this meta model, the system then creates the Java classes which are executed at runtime on the J2EE Engine in the SAP Web Application Server. For more complex applications, you are required to make some adjustments and changes to the source code generated. In special areas marked as such, you can edit the code generated and implement you own code there.
Model View Controller Paradigm
The model view controller paradigm (MVC paradigm) is based on a clear separation of business logic and presentation logic.
• The model represents the business logic and the persistence on the backend.
See also Model and Java Dictionary.
• The view is the central logical element for the layout and the processing of the presentation logic.
See also View – Programming UI and Navigation.
• The controller is responsible for programm control, determining the data flow between the view and the model and handling events.
Web Dynpro Tools
The Web Dynpro perspective in the NWDS provides various graphical tools. The Web Dynpro Explorer, for example, has a tree structure which provides a logical view of the DC or the Web Dynpro project. Model tools help you to implement the data access and the business logic, and the View Designer supports you with designing the layout.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.