MVC ARCHITECTURE

[Former Member]

Hello all

Can you please explain what is MVC according to SAP,

Thanx in advance

Sijju

[Former Member · Accepted solution]

Hi

Check this

forum

1 .

2 .

help.sap

1 . http://help.sap.com/saphelp_nw2004s/helpdata/en/0f/ab3a3c9ca75402e10000000a114084/frameset.htm

Regards

Abhijith YS

[Former Member]

Hi Thanks a lot

is it same as java mvc or is there any difference

Thanks

Sijju

[Former Member]

Hi,

The MVC is the same but SAP has simple modified in some technolgies like webdynpro for their convience.

for reusability of business functionality they are combined the View and controller as a component.

That componenet is defined as unit of code or unit of business functionality and it contains view and controller.

Thanks,

Lohi.

[Former Member]

chk it

http://help.sap.com/saphelp_nw04/helpdata/en/0f/ab3a3c9ca75402e10000000a114084/frameset.htm

http://help.sap.com/saphelp_nw04/helpdata/en/1d/20693c4b1c6646e10000000a11402f/frameset.htm

http://help.sap.com/saphelp_nw04/helpdata/en/02/3f443ca607d75ce10000000a11402f/frameset.htm

[Former Member]

Hi Sijji,

MVC stands for Model View Controller..

MVC Architecture is designed for decoupling presentation and application logic.

the below definitions will explain you better.

<b>Model:</b>

Generates the application data without caring how it will be displayed.

<b>View:</b>

Visualizes the application data without caring how it was generated.

<b>Controller:</b>

Binds the user and business interaction layers together. All intermediate rocessing

is performed here. It acts as an iterface between Model and View.

Webdynpro uses this architecture to implement User Interfaces.

SAP has made several important changes to the standard MVC design paradigm:

Standard MVC allows a model to directly notify a view that it has changed. This has not been implemented in Web Dynpro.

Standard MVC allows for nested view controllers. This is not permitted in Web Dynpro.

SAP has extended the design concept by adding an aggregation unit known as a component. The component is both the unit of application development and application reuse.

You can refer below links for more information about MVC.

http://help.sap.com/saphelp_nw70/helpdata/en/02/3f443ca607d75ce10000000a11402f/frameset.htm

http://help.sap.com/saphelp_nw70/helpdata/en/42/9de349bb211d76e10000000a1553f6/frameset.htm

Regards,

Naresh

Message was edited by:

Armin Reichert

[Former Member]

Hi

Definition

The model view controller paradigm (MVC paradigm) is based on a clear separation of the functions of data model (model), presentation logic (view), and program control (controller).

In Web Dynpro, the function of the model has been extended beyond a mere persistency layer. In a Web Dynpro model, you can encapsulate functions that represent an entire business process.

Model

The Web Dynpro developer can define a model for retrieving data as well as for integrating business logic.

View

The view is responsible for the graphic display of the data. Within Web Dynpro, the view element of the MVC paradigm is represented by the logical units view set and view and the UI elements contained in them. View designers always work with logical interface objects, although they can also access the Java source text directly, for example to generate the UI automatically and to have additional coding run at runtime.

Controller

The controller is responsible for the program control. It controls the flow of data between view and model and handles events.

In Web Dynpro, the role of the controller is divided among several controllers:

· View controllers that are directly assigned to a view,

· A component controller as the central instance to which you can add other custom controllers,

· An interface controller that makes its data available to a higher-level component.

Regards

Abhijith YS

[Former Member]

Hi Sijji,

<b>a.MVC Pattern</b>

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.

• The view is the central logical element for the layout and the processing of the presentation logic.

• The controller is responsible for program control, determining the data flow between the view and the model and handling events.

<b>b.Model</b>

This section provides an overview of data retrieval and business logic encapsulation in a Web Dynpro application.

You can use various different data sources for your Web Dynpro application. For a simple connection of a model, wizards are available that generate the relevant classes for your application.

You can define several models for each application. In a model declaration you define which model is to be the valid interface at runtime. With this reference, the application entity Web Dynpro component is addressed.

The controllers are responsible for the data flow between the model and the other Web Dynpro entities. The data transport between the model and the controller is referred to as model binding – that is, there is a reference to the back-end data in the Web Dynpro application.

<b>c.View (All types)</b>

Graphical tools are available for designing and implementing the user interface. The Navigation Modeler provides support when you create the logical interface elements (known as views) for the Web Dynpro application; it also supports the arrangement of these views on the screen. With the view definition you create an element that firstly acts as a container for your Web interface definitions and secondly contains the active part, the context. You then assign the elements to the interface and supply them with data;

<b>d.Controller (All types)</b>

The controller is responsible for program control, determining the data flow between the view and the model and handling events.

There are different types of controllers:

• A view controller is directly assigned to a view.

• The component controller is the central instance to which you can add other custom controllers. These controllers interact with the model.

• An interface controller makes its data available to a higher-level component.

Regards,

Murtuza