Using Interface controller in OCA application

Hi,
My requirement is to pass information and screen control between two components in two different DCs.
My parent DC Component has to pass information to my child DC Component and also call the view assembly of the child DC.
I am using CE7.1 SP07 PAT003.
In my child DC I have created a component Interface Definition say ChildInterface. In the context of interface controller of ChildInterface I have added a string attribute. ChildInterface also has a view container.
Now in my Child component I add ChildInterface as my Implemented Interface. I map the window of the child component to the ChildInterface. To the view container I add the default view of the component.
Now I have created a public part and added the ChildInterface as an entity.
I add a dependency in my Parent Component to this child DC's public part.
At design time I can access my ChildInterface's context from my parent component. However, while adding a link from parent default view to ChildInterfaceView, it gives me an error. however on reload it suppress the error but doesnt open the java editors.
While trying to deploy the applications it gives me a deployment failure message.
Following is the trace-
<r id="1240744927041" t="16:52:07" d="2009-04-26" s="E" c="000" u="" g="" m="Missing app.xml in component C:\Program Files\SAP\IDE\CE\eclipse\plugins\com.sap.tc.mobile.dt.oca.rt\MI\bin\..\inbox\demo.sap.comparentimplementation\demo.sap.comparentimplementation.wdl">
<f n="LocationName" v=" (com.sap.tc.mobile.cfs.deploy.oca.OCADeployer:OCADeployer)"/>
<f n="ThreadName" v="main"/>
</r>
<r id="1240744927042" t="16:52:07" d="2009-04-26" s="E" c="000" u="" g="" m="Deployment of Mobile Component parent(1.0) failed --> java.io.IOException: Missing app.xml in component C:\Program Files\SAP\IDE\CE\eclipse\plugins\com.sap.tc.mobile.dt.oca.rt\MI\bin\..\inbox\demo.sap.comparentimplementation\demo.sap.comparentimplementation.wdl
 at com.sap.tc.mobile.cfs.deploy.oca.OCADeployer.deploy(OCADeployer.java:81)
 at com.sap.tc.mobile.cfs.deploy.DeploymentManager.processDeploymentStatusObjects(DeploymentManager.java:550)
 at com.sap.tc.mobile.cfs.deploy.DeploymentManager.processInbox(DeploymentManager.java:197)
 at com.sap.tc.mobile.cfs.init.FrameworkInitializer.init(FrameworkInitializer.java:192)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at com.sap.tc.mobile.cfs.startup.pda.Startup.main(Unknown Source)
">
<f n="ThreadName" v="main"/>
</r>
<r id="1240744927695" t="16:52:07" d="2009-04-26" s="E" c="000" u="" g="" m="Resourcebundle sap.comtcmobilewdlitecontainer could not be found. Trying to use the default bundle.">
<f n="LocationName" v=" (com.sap.tc.mobile.wdlite.renderer.exception.OCAExceptionLocalizeHelper:)"/>
<f n="ThreadName" v="main"/>
</r>
<r id="1240744927696" t="16:52:07" d="2009-04-26" s="E" c="000" u="" g="" m="Internal Error. Please check the log file. --> java.lang.NoSuchMethodException: com.sap.tc.mobile.wdlite.framework.Start.setUpSystemMenu()
 at java.lang.Class.getMethod(Class.java:1581)
 at com.sap.tc.mobile.wdlite.progmodel.core.Application.resetSystemMenu(Application.java:260)
 at com.sap.tc.mobile.wdlite.progmodel.core.Application.enter(Application.java:242)
 at com.sap.tc.mobile.wdlite.progmodel.core.Application.setCurrent(Application.java:119)
 at com.sap.tc.mobile.wdlite.progmodel.core.Application.launch(Application.java:143)
 at com.sap.tc.mobile.wdlite.progmodel.core.Application.launch(Application.java:175)
 at com.sap.tc.mobile.wdlite.progmodel.core.WDLite.launchApplication(WDLite.java:334)
 at com.sap.tc.mobile.wdlite.framework.Start.runOnContext(Start.java:580)
 at com.sap.tc.mobile.wdlite.framework.Start.startApplication(Start.java:604)
 at com.sap.tc.mobile.wdlite.framework.Start.startContainer(Start.java:641)
 at com.sap.tc.mobile.cfs.framework.spi.FrameworkManager.startContainer(FrameworkManager.java:259)
 at com.sap.tc.mobile.cfs.init.FrameworkInitializer.init(FrameworkInitializer.java:230)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at com.sap.tc.mobile.cfs.startup.pda.Startup.main(Unknown Source)
">
<f n="ThreadName" v="main"/>
</r>
<r id="1240744927697" t="16:52:07" d="2009-04-26" s="E" c="000" u="" g="" m="Internal Error. Please check the log file.">
<f n="LocationName" v=" (com.sap.tc.mobile.wdlite.renderer.exception.OCAExceptionHandler:)"/>
<f n="ThreadName" v="main"/>
Please help.
Regards,
Nisha

please do attach the trace files..
Meanwhile , just check the way you have implemented the interface and the interface defintion of achild node are correct.
Once the implementations are correct,there should not be problem in deployment.
Let us know if you need more info on interface definton creation ...
Regards,
Lakshmi
Edited by: Lakshmi Reddi on May 28, 2009 6:03 AM

Similar Messages

Code example using interface controller ?

Hi, guys:
I have a question.
In CRM UI, I need to integrate one component with another component, and I want to pass the value from 1st component to 2nd component using interface controller. Does any one who have done this before and have a code example?
Really appreciate!
Eric

Hi Eric,
Refer:
[http://forums.sdn.sap.com/thread.jspa?threadID=2014259|http://forums.sdn.sap.com/thread.jspa?threadID=2014259]
[http://forums.sdn.sap.com/thread.jspa?threadID=1909625|http://forums.sdn.sap.com/thread.jspa?threadID=1909625]
Regards,
Leon

In which situvation you will use interface controller and custom controller

in which situvation you will use interface controller and custom controller?

Hi rafi,
Custom Controller Custom Controller is as same as the component controller, here we can write the business logic.
Custom Controller means developer can create multiple controller denpeing up work.
By using component controller we cant create multipule contrllers. when we create the DC that time it will be created automatically.
Please look at this [Link|http://help.sap.com/search/highlightContent.jsp]
interface controller
Communication between two componets by using interface controller.
Please look at this [ Thread|Commmunication Between two Components;
Regards
Vijay Kalluri

Interface Controller of a Component

Hi,
Can anyone explain/provide any doc which explains using one component in another component using interface controller.
Warm Regards,
Imtiyaz

Hi,
Refer these links,
WebDynpro Componentization [original link is broken]
https://www.sdn.sap.com/irj/sdn/index?rid=/webcontent/uuid/c053bcfa-426e-2910-f28a-91dec33159d6 [original link is broken]
http://help.sap.com/saphelp_nw04/helpdata/en/15/0d4f21c17c8044af4868130e9fea07/content.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f727d100-0801-0010-4cbd-b0ad5c161945.
/people/sudhir.gorantla4/blog/2008/02/27/componentization-of-webdynpro-application-in-ce71
Regards,
Sunaina Reddy T

Thruster control using PID controller

Dear All,
Actually my project is related to heading control of an underwater system using PID controller - A Labview Application.
Till now, As per this forum discussion, I have completed the rotation count measurement of a compass C-100 device using Event structure and cFP controller.
Now I need to integrate the PID controller for thruster control according to the count value measured.
Could you please anyone guide me to start implementing the same. Please do the needful.
Thanks and Regards,
Dinsulpri.

Dear nathand,
Actually I need do a heading control application of a underwater system by using PID controller by the help of thrusters.
According to this,Firstly,I have completed the rotation count measurement of the system by interfacing the compass C-100 (for checking) with the cFP controller.It is working fine.
Now I need to do the PID controller part based on this count value measures, that is , I need to give the control signal to the thruster in order to release the twist of the system.
I just gone through the PID part in the labview and understood the concept and simulated the basic examples given in that.
My Understand as follows, Please validate the same and give me your suggesion on this,
1) Need to give Setpoint should be a thruster voltage .
2) I dontknow what to give in the process variable field.
3)Apart from this, how can I show this concept schematically with out connecting the thruster manually? Is it possible to show the demo in chart analysis format?
Please validate the above points and guide me to start working on this task.
The rotation count measurement application, Till now I did was attached with this. Please go through the same.
Thanks and Regards,
Dinsulpri.
Attachments:
Compass_Event Structure.vi ‏18 KB

Difference between interface view and interface controller

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

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-c87806865f26?rid=/library/uuid/49f2ea90-0201-0010-ce8e-de18b94aee2d#13 [original link is broken]
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/webcontent/uuid/28113de9-0601-0010-71a3-c87806865f26?rid=/library/uuid/49f2ea90-0201-0010-ce8e-de18b94aee2d#12 [original link is broken]
Interface view and interface controller
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f727d100-0801-0010-4cbd-b0ad5c161945
Difference between custom controller and interface component
Thanks and Regards,
Tulasi Palnati

Using Interface controllers

hi friends,
i have two DC's , i want use one DC data in another DC .how to use it using interface controller and sample code.
thanks in advance.
krishna.

Hi
A step by step approach
1. Create DC1 call it parent DC and DC2 child DC.
2. Create a same context node in view controllers of DC1 an DC2 and same node in the Interface Controller of DC2 component.
3. Map the values between view controller and Interface Controller of DC2.
4. Create public part in DC2 then build & deploy it.
5. Now in DC1 which is parent Component, here use DC2 component's public part in USED DC's of DC1 component.
6. Goto Used Web Dynpro Components and Add Used Component (which is Dc2 Component)
7. Open DC1ComponentWindow and Embed DC2 View using "Embed Interface View of a Component Instance"
8. Now open Data Modeler of DC1 Component there you will get DC2 component under Used Web Dynpro Components.
9. Map values of Context Node between Used Interface Controller of DC2 and View Controller of DC1
(You may create a navigation link between views of both view controllers to test it)
10.build your DC1 and deploy it
Mandeep Virk

Context from interface controller

Hi Experts,
I am Using one DC A in DC B.
Using interface controller context mapping I got the Context of DC A in DC B.
I mapped the context also.
Now I have added new context node in DC A, I want map it in DC B.
But I am not able to see the newly added Context of DC A in the interface contrlloer.
I have done refresh, rebuild and Sync options but no use.
How can I resolve this?
Regards,
Naresh

Hi,
Copy and paste the newly created context from component controller to interface controller
Then do a build.
Regards
Ayyapparaj

Interface controller implementation

Hi
i have two component controllers i iwant to call ametod from compenent controler1 to commponent controller2 using interface controller,can you please explain it with sample example.
Thanks
Kumar

Rahul,
This is not related to Adobe forms, so please close this thread.
I sugegst please post the question in Web Dynpro (JAVA/ABAP) forums or search SDN and you should get the results.
Chintan

Loading metadata into EPMA applications using Interface tables-Automation

Hi,
I am loading the metadata into epma applications using interface tables as ODI dont perit to load metadata into epma applications. Is there any way of using ODI and interface tables together to load the metadata
This process also need to be automated.

Hi,
It is certainly possible and has be done, though there is not anything available that will do it for you, you will have to put in some effort learning the structure of the interface tables, then build interfaces and then a package in ODI to streamline the process.
Cheers
John
http://john-goodwin.blogspot.com/

Use of interface controller

HI
can u please explain me use of interface controller with simple example along with the code
Thanks
kishore

Hi Kishore,
Here r the few facts abt interface controller:-
Used to control access from other components.
Is created automatically when a component is created.
Exists as long as its component is embedded in another
component.
This controller contains data, methods, and events that can be used by other Web Dynpro components.
A componentu2019s interface controller can be used by the embedding component for mappings, eventing, etc.
Interface for external users of a component: data transfer,
eventing.
Interface Controller
One Web Dynpro Component may declare the use of another Web Dynpro Component to form a u201CParent-Childu201D usage relationship. In such cases, the only point of interaction between the parent and child components is the functionality found in the childu2019s interface controller.
There is a usage declaration arrow pointing from the component controller to a child component. Notice that the arrow joins the child component at the top right-hand corner. This is the location of the childu2019s interface controller.
At no time does the Web Dynpro Runtime interact with a componentu2019s interface controller. It is only ever used to form a Parent-Child relationship between two Web Dynpro Components.
Check the links:-
http://help.sap.com/saphelp_nw70/helpdata/EN/47/45641b80f81962e10000000a114a6b/frameset.htm
http://help.sap.com/saphelp_nw70/helpdata/EN/44/0dcafa2d9d1ca2e10000000a11466f/frameset.htm
hope dat may help u..
Regards,
Deepak

API's used in Interface programs of Oracle Applications

hi
can any one let me know about the PL/SQL API's that are used in interface programs of oracle applications.
in what cases we are using them
and if possible their syntax
thanks in advance
bye

Pl Sql APIs are used for uploading / correcting the mass Data of Oracle HRMS and Oracle Payroll , For Technical person they are Fast and Easy for data Migration Purpose
You Can Seach more on Metalink.
You can search these APIs from your Data Base where name like '%API'

Using EJBs in Web Dynpro Applications

I have recently started to develop Web applications using the Web Dynpro framework. Coming from a pure J2EE world, I must admit that Web Dynpro has a few innovative features that I find interesting for user interface development. The use of component & view contexts, for example, is not unlike the ActionForms that one may find in a Struts application, but pushed a bit further. No complaints here.
What I do have some problems with is the whole CommandBean paradigm that is put forth by SAP (refer to the document <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/webdynpro/using%20ejbs%20in%20web%20dynpro%20applications.pdf">Using EJBs in Web Dynpro Applications</a>).
I do understand the usefulness of defining a model that will be used to generate and eventually bind to Context data structures. That's fine. What I do object to is the use of a so-called CommandBean to play that role. Again, coming from a J2EE world, I am familiar with the BusinessDelegate pattern - which would typically be used by a client application to invoke business logic on the server side. I would propose that a better, cleaner way of integrating EJBs with the Web Dynpro framework would be to use a BusinessDelegate for invoking business logic, and importing a separate and distinct ModelBean (instead of a CommandBean) to be used for defining and binding to Context data.
I have built one Web Dynpro application thus far. Instead of using a CommandBean, I created a ModelBean that extends my business object DTO (Data Transfer Object) (which is quite appropriate for that role, given that it implements all the get & set methods that are required for the business data that I need to model). My Web Dynpro application also makes use of an independant BusinessDelegate that is packaged with my EJB DC - this is a standard best practice on J2EE projects. I have been asked by the people working with me to modify this architecture to bring it more in line with the SAP way of doing things. I am open-minded and willing to learn and accept new ways of thinking and doing things. However, I fail to understand the usefulness of merging structure and behaviour by resorting to CommandBeans:
- It violates the MVC paradigm by having one object (the CommandBean) serve as both model AND controller as far as the Web Dynpro application is concerned. The CommandBean is obviously a model - since it is literally imported as such into the Web Dynpro application. It is ALSO a controller from the Web Dynpro's application perspective, since all calls to the back-end go thru the CommandBean via one or more of its execute_xxx methods. In contrast, the use of a business delegate by the Web Dynpro application clearly separates the model (the CommandBean... or rather, a more suitably named ModelBean) from the controller (BusinessDelegate).
- Doesn't carry its own weight. In other words, I haven't yet been provided with any valid justification for going thru the extra effort of coding the CommandBean's execute methods. It's been proposed to me that it somehow serves as an abstraction layer between the Web Dynpro application and the business logic. I would argue that it is the BusinessDelegate's role to abstract away the back-end logic from clients. If one does have a BusinessDelegate available, I would argue there's no need to code execute methods in a separate CommandBean. To prove my point, I would simply point out that all of the CommandBean examples that I have seen so far, either in How-To documents, or in production code, all follow the same pattern....
CommandBean.execute_doSomething() calls BusinessDelegate.doSomething()
Not a heck of an "abstraction" layer... I would in fact argue that it is worse than useless. If some major change occurs in the business logic that requires changing the doSomething() operation, we expect of course to modify the BusinessDelegate. The Web Dynpro client will also presumably need to be modified - that's to be expected, and unavoidable. But then, we'll also need to go about and change the CommandBean's execute_doSomething() method - again, extra work for no apparent benefit. Adding and removing business methods has the same implication. All this for an layer that simply adds the prefix execute_ in front of all business method calls... Is this "abstraction layer" worth the cost of creating and maintaining it ??
- Unnecessarily complicates error handling. I have been told that for technical reasons, it is recommended that all exceptions thrown by the CommandBean be of type WDException or WDRuntimException. But what if the client application needs to react differently to different failure scenarios ? When I create a business object, I might wish to provide the user with an error messages if connection is lost to the backend, and with a different error message if an object already exists in the database with the same attributes. In order to do that, I will have to catch the WDException, extract the cause, and continue processing from there... possible, yes, but clearly less standard and more labor intensive than the classical try/catch mechanism.
To say nothing about the fact that SAP's own API documentation clearly states that applications using Web Dynpro can reference and catch WDExceptions, but THEY MUST NOT THROW OR EXTEND IT !
- Produces unnecessary DCs. Page 6 of the aforementioned document presents an architectural view of a Web Dynpro project that uses a CommandBean. Why an extra DC for the CommandBean ?? I created my ModelBean class right inside the Web Dynpro project (in the Package view). That, to me, is where this class should reside, because it is created for no other reason that to be used by this particular Web Dynpro application. What is the benefit of placing it in its own independant DC ?
- Not a typical application of the Command pattern. The well-documented command pattern (Design Patterns - Gang of Four) has been devised mainly to enable encapsulation of request as objects, thereby making it possible to:
- specify, queue and execute requests at different times
- decouple execution of a command from its invoker
- support undo operations
- support logging changes so that they can be reapplied in case of system crash making it possible to assemble commands into composite commands (macros), thereby structuring a system around high-level operations built on primitive operations.
None of this applies to the way the SAP CommandBeans are being used. Not that much of an issue to people new to J2EE and/or OO development... but quite confusing for those already familiar with the classic Command pattern.
At this point, I fail to understand the advantage of merging structure (model) and behaviour (execute methods) through the use of a unique CommandBean object. Am I missing something ?

Hi Romeo,
You would be disappointed, this reply ain't anywhere nearby to what you are talking about...
I wanted to mail you, but you have not mentioned your email in your profile.
I am really impressed by your flair for writing. It would be far better had you written a blog on this topic. Believe me, it would really be better. There is a much wider audience waiting out there to read your views rather than on the forums. This is what I believe. To top it, you would be rewarded for writing something like this from SDN. On the blogs too, people can comment and all, difference being there you would be rewarded by SDN, here people who reply to you would be rewarded by you. Doesn't make much a difference.
Anyways the ball is still in your court
As far as I am concerned, it has still not been much time since I have started working on Web Dynpro. So can't really comment on the issue...
Bye
Ankur

How to instantiate a control in code instead of using Interface Builder ?

I really appreciate the combination of the interface builder and Xcode altogether.
However when I am learning QT, I realize I had been pampered by Apple's Design to a certain extend as I only need to create say a NSLabel instance and use Interface Builder to do the linking and never have to worry about instantiating the Object myself.
But I'm curious, what is the way to instantiate a new hmmm say...NSLabel in the code ?
NSLabel* label = new NSLabel();
Then what ?
What you are seeing here is how QT did it, could anyone create an equivalent in ObjC ? No fancy code please, just bare minimum.
#include <QApplication>
#include <QWidget>
#include <QLabel>
int main (int argc, char * argv [ ])
QApplication app(argc, argv); //NSApplication in ObjC
//These two lines merely created a window and set the title bar text.
QWidget* window = new QWidget();
window->setWindowTitle("Hello World");
QLabel* label = new QLabel(window);//Create a label and inform the it belongs to window.
label->setText("Hello World");
window->show();
return app.exec();
Message was edited by: Bracer Jack

Hi Jack -
I think my best answer will be something of a disappointment, because I don't know how to show a one-to-one correspondence between the code you're working with and a Cocoa program. The main function of a Cocoa GUI program for OS X will look something like this:
#import <Cocoa/Cocoa.h>
int main(int argc, char *argv[])
return NSApplicationMain(argc, (const char **) argv);
As you commented, we could draw a correspondence between the first statements, but after that the functionality of the Cocoa program is going to be spread out in a way that makes for a rather tedious comparison. The only way I know to answer your question in less than 5000 words, is to skip ahead to one of several points in the startup sequence where the programmer can intervene with custom code.
For example, a common way to get control would be to program a custom controller class and add an object of that class to the main nib file which is loaded during the startup sequence. By making a connection to the Application object in that nib file, the custom object could be made the delegate of the Application object, and if we then added a method named applicationDidFinishLaunching, our code would run as soon as the application's run loop was started.
Now I finally have enough context to directly answer your question, so here is the code to create a label and add it to the key window at launch time:
// MyAppController.m
#import "AppController.h"
@implementation AppController
- (void)applicationDidFinishLaunching:(NSNotification *)aNotification {
NSLog(@"applicationDidFinishLaunching");
NSRect frameRect = NSMakeRect(150, 300, 150, 30);
NSTextField *label = [[NSTextField alloc] initWithFrame:frameRect];
[label setEditable:NO];
[label setStringValue:@"Hello World!"];
[label setFont:[NSFont labelFontOfSize:20]];
[label setAlignment:NSCenterTextAlignment];
NSView *contentView = [self.window contentView];
[contentView addSubview:label];
@end
If I needed to develop a worst case scenario for this thread, the next question would be, "Ok sure, but your code still needs a nib to start up. I want to see a Cocoa GUI program that doesn't require any nib".
It turns out that it's quite easy to build a simple iPhone app without any nib, but it's considerably more difficult for an OS X app. If anyone wants to see my nib-less iPhone code, I'll be happy to post it (I think I did post it here once before, and the response was underwhelming). But I've never attempted the much more difficult nib-less OS X app. Just in case you really want to go there, here's a blog that goes into the details: [http://lapcatsoftware.com/blog/2007/07/10/working-without-a-nib-part-5-open-re cent-menu>.
Hope some of the above is helpful!
- Ray

How to create a method in Interface Controller

Hi Guys,
        I am working with webdynpro ABAP sample application "Component usage" . There i got a issue like i am not able to create a method in Interface controller. There i am not able to edit anything. Can anybody please let me know how to do that.
            Thanks In Advance
Regards
Ravikumar

Hi Ravi,
          Check This
If one Web Dynpro component (parent component) needs access to another Web
Dynpro component (child component) the parent component can declare the use
of the child component. A specific component usage instance is then created and
the parent component accesses the functionality of the child component via its
component interface controller.
The only parts of a Web Dynpro component that are visible to the user, are the
interface controller and the interface view(s).
All Web Dynpro components have only one interface controller. Via the
interface controller, data, methods, and event handlers can be exposed to
other components.
Interface views represent the visual interface of a Web Dynpro component.
There is a one-to-one relationship between a Window and an interface view.
Each time a window is defined, a related interface view is automatically
generated, which makes the window accessible from outside the component.
The interface view only exposes those inbound and outbound plugs to the
component user that have the interface property checked. Methods and
context data of the window are not accessible via the related interface view.
If the component has no views, there is no need to have Windows. In this
case, the component will not implement an interface view. Such components
having no visual interface are known as faceless components.
Regards
Sarath

Using Interface controller in OCA application

Similar Messages

Maybe you are looking for