Difference between interface view and interface controller

[Former Member]

Hi,

What is the difference between interface controller and interface view?

When we will use interface controller and when we will use interface view?

How do we create an interface view?

How do we attach this interface view to a view in another component

Regards

MQ

[Former Member]

Hi,

As WebDynpro is based on MVC architecture, so everything in WebDynpro is reusable. WebDynpor Component is an reusable component. So a WDComponent can interact with another WDComponent using the InterfaceView and InterfaceController.

InterfaceView - To Navigate to another Component's View

InterfaceConterlloer - To transfer/ expose the data (through context) and to exposte the methods to another WDComponent.

WebDynpro Component:

A WebDynpro component is Unit of work or unit of reuse. As WebDynpro is mainly based on MVC architecture every part of WebDynpro is reusable. For example you developed a WebDynpro component for some common functionality like "Check account validity". You can reuse this component in any other WDComponents for the same functionality. You need not to implement again.

WebDynpor Windows & Views:

A WD ViewController is to implement the presentation layer nothing but the UI elements. It can be devided into two parts.

View - ( Layout ) - To create the UI elements

Controller - (Context, Actions, Controller Usage, Plugs, Methods & Evenhandlers and Implementation)Implementation purpose

A WD Window will be associated with an InterfaceView. You can create multiple Windows in a WD Component. And you can embed multiple Views in a single window.

Only one Window will be the default for any WD Application. Then what is the need of multiple windows?

This is because you can create different WD Applications for different windows with in a single WDComponent.

App1 - WDComp1 - WDInterfaceView1 - WDWindow1 - WDView1

App2 - WDComp1 - WDInterfaceView2 - WDWindow2 - WDView1

Hope this information helps to understand WebDynpro.

See this below pdf for structural concepts of WebDynpo.

https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a048387a-0901-0010-13ac-87f9eb64...

Regards,

Charan

[Former Member]

Hi

Interface View Controllers

A) Implement event handlers which are called when ..

-starting (start-up plugs) Web Dypro applications

-a component is reached via navigation (inbound plugs)

B) Allow fireing outbound plugs (navigation)

C) Allow firing exit plug

D) Have no own context, public methods or events

Interface Controller of a Component

The interface controller of a Web Dynpro component contains all context nodes, events and methods of the component controller to which you assigned the Interface addition in the Controller Editor. These parts can be displayed in the interface controller view, although you cannot edit them here.

Interface Controller of a Component Interface

A Web Dynpro component interface can be created independently and defined so that it can be implemented later in any components (see working with Web Dynpro Component Interfaces in the Programming Manual of this documentation). That is why in this case you can define the context nodes, methods and events you require in the interface controller view. The relevant implementation then takes place in the component controller of the implementing component.

Check this links and work on it.

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/webcontent/uuid/28113de9-0601-0010-71a3-c8780... [original link is broken]

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/webcontent/uuid/28113de9-0601-0010-71a3-c8780... [original link is broken]

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f727d100-0801-0010-4cbd-b0ad5c16...

Thanks and Regards,

Tulasi Palnati