on 12-01-2004 7:05 PM
Hi
I have a scenario where a Parent window calls a child window and that child window calls one more child window.
I developed a component which contains a view that is to be displayed in all the windows. This view is embedded into every window view set.
When i try to run the application, it gives me a runtime exception.
Is there any solution/work around for this?
Find below the exception raised.
Error stacktrace:
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Duplicate instance exception: There is already an instance of interface view WD_MessageHandlingInterfaceView in component CO_MessageHandling.
at com.sap.tc.webdynpro.progmodel.controller.Component.addInterfaceViewController(Component.java:150)
at com.sap.tc.webdynpro.progmodel.view.InterfaceView.initController(InterfaceView.java:45)
at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:540)
at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:398)
at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:555)
at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:422)
at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:130)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.doOpen(WebDynproWindow.java:198)
at com.sap.tc.webdynpro.clientserver.window.InternalWindow.open(InternalWindow.java:45)
at org.wb.sample.ParentSearchDemoView.general(ParentSearchDemoView.java:231)
at org.wb.sample.ParentSearchDemoView.onActionPopup(ParentSearchDemoView.java:323)
at org.wb.sample.wdp.InternalParentSearchDemoView.wdInvokeEventHandler(InternalParentSearchDemoView.java:230)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleAction(WebDynproMainTask.java:100)
at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:299)
at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:635)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:249)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:821)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
Thanks in advance.
Regards
NagaKishore V
Hi
I faced same problem. It seems that the child window (internal) can not contain same view (whatever the view is in same component or different component as the window) as which its parent window contained. Is it true?
Thanks in advance.
Hongyuan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi NagaKishore,
How do you close child window? If you use window.close() try window.destroy(). We had similar exception with child windows and after using destroy() exception disappeared.
Andrei
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Nagasan
Are you getting the error the first time you activate the pop up or on subsequent activations.
Your error points to a situation where the interface view of your component exists in memory and you are trying to create it again.
Are you destroying the window after the close using .destroy(). What about the component usage is it manual or framework controlled. With manual you can control the creation and destruction of the component
Regards
Pran
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
80 | |
24 | |
11 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.