runtime error: failed to create delegate view

[Former Member]

hi all,

We have two applications in two separate projects. But we can deploy only one at a time. If we deploy the second application (or vice-versa)and try to access the first application, it throws up the following error.

P.S. The problem is only with these two applications and they use Adaptive RFC models.

We thought it was because of some Jco conections, but all of them test correctly from the WebDynpro administrator console. Any ideas?

Error stacktrace:

com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to create delegate for view com.eac.vendorportal.DisplayNCRView. (Hint: Is the corresponding DC deployed correctly? Does the DC contain the component?)

at com.sap.tc.webdynpro.progmodel.generation.ControllerHelper.createDelegate(ControllerHelper.java:110)

at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.<init>(DelegatingView.java:41)

at com.sap.tc.webdynpro.progmodel.view.ViewManager.createUninitializedView(ViewManager.java:487)

at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:524)

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.progmodel.view.InterfaceView.initController(InterfaceView.java:41)

at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)

at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.displayToplevelComponent(ClientComponent.java:134)

at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:373)

at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:608)

at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)

at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:252)

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.doGet(DispatcherServlet.java:48)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:392)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:345)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:323)

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:865)

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:240)

at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)

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:95)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:159)

Caused by: java.lang.ClassNotFoundException: com.eac.vendorportal.wdp.InternalDisplayNCRView

Found in negative cache

-

---

Loader Info -

---

ClassLoader name: [local/ChangeNCR4]

Parent loader name: [Frame ClassLoader]

References:

common:service:http;service:servlet_jsp

service:ejb

common:service:iiop;service:naming;service:p4;service:ts

service:jmsconnector

library:jsse

library:servlet

common:library:IAIKSecurity;library:activation;library:mail;library:tc_secssl

library:ejb20

library:j2eeca

library:jms

library:opensql

common:library:com.sap.security.api.sda;library:com.sap.security.core.sda;library:security.class;library:webservices_lib;service:adminadapter;service:basicadmin;service:com.sap.security.core.ume.service;service:configuration;service:connector;service:dbpool;service:deploy;service:jmx;service:jmx_notification;service:keystore;service:security;service:userstore

interface:resourcecontext_api

interface:webservices

interface:ejbserialization

sap.com/tc_wddispwda

sap.com/tc_wdcorecomp

service:webdynpro

service:sld

library:tc_ddicddicservices

library:com.sap.aii.proxy.framework

library:tc_graphicsigs

library:com.sap.mw.jco

library:com.sap.lcr.api.cimclient

library:sapxmltoolkit

library:com.sap.aii.util.rb

library:com.sap.util.monitor.jarm

library:tc_ddicddicruntime

library:com.sap.aii.util.xml

library:tc_colapi

library:com.sap.aii.util.misc

library:tc~cmi

library:tc_colruntime

Resources:

F:\usr\sap\PED\JC00\j2ee\cluster\server0\apps\local\ChangeNCR4\webdynpro\public\lib\app.jar

Loading model: {parent,references,local}

-

---

at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:348)

at com.sap.tc.webdynpro.progmodel.generation.ControllerHelper.createDelegate(ControllerHelper.java:65)

... 33 more

[BeGanz]

Hallo Vamsee,

a "failed to create delegate" error is often based on the fact, that there is no component instance for a certain component usage. The usage points to null but the embedder requires a component/controller instance.

You describe a two-application scenario. How does it look like. Two Web Dynpro applications in separate projects do not know each other. What do you mean with 'access the first application'?

Regards, Bertram

[Former Member]

Bertram,

I have two WebDynpro iviews which are based on those two applications. "accesing" simply means browsing those iViews in the portal.

the two applications are in entirely different projects.

the only thing they have in common is some JCo references.

P.S. We use the same package naming conventions in both projects.Is that a problem?

Vamshi

[Former Member]

Hello,

I guess you are using your component 1 present in Project 1 as a used component in component 2 of Project 2.

If my understanding is correct, then you would have defined your component 1 as a PublicPart (PP).

Check the "_comp\gen\default\public" folder of the component 1. You should find the corresponding jar files of the Public Parts. If the jar files are not there, go for a DC Build.

Bala

[BeGanz]

Hallo Vamsee,

you wrote <i>"We use the same package naming conventions in both projects.Is that a problem"!</i> Does this mean that you have two different DCs sap.com/a/b/c/onedc and sap.com/a/b/c/anotherdc which both contain the same Web Dynpro component packages e.g. com.sap.a.b.c.mycomp? If this is true both Deployable DC units will collide on the serverside because the Web Dynpro classloader does not differ between the same Web Dynpro packages in different DCs. The DC namespace is not reflected by the classloader.

Regards, Bertram

[Former Member]

I have already tried restarting the server. doesnt help

[Former Member]

Hello,

Try deleting the "gen_wdp" and the "bin" folders of your

project and do a "Reload+Rebuild". This should solve

your problem.

<i>Please reward appropriate points.</i>

Bala

[Former Member]

bala,

That did not resolve the dependency between these two applications. weird and i am still working on it. will keep u updated

Vamshi