Did not find repository information for controller

[Former Member]

I writing an application into WebDypro, which updates Z TABLES thru custom BAPI’s. After deployment of an application I am getting an exception

com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Did not find repository information for controller PutOnHold

When I redeploy the same application my application works for some 10 minutes and then again I gets same exception. I checked duplications of application names and other duplications like custom controller names. There is no application with duplicate names exits in my WebDynpro browser.

My complete stack trace is

Detailed Error Information

Detailed Exception Chain

com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Did not find repository information for controller PutOnHold

at com.sap.tc.webdynpro.progmodel.controller.Component.getController(Component.java:351)

at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.getPublicInterface(DelegatingComponent.java:142)

at com.epson.rfq.direct.wdp.InternalRFQDirectCustView.wdGetPutOnHoldController(InternalRFQDirectCustView.java:582)

at com.epson.rfq.direct.RFQDirectCustView.onActioncreatePutOnHold(RFQDirectCustView.java:1799)

at com.epson.rfq.direct.wdp.InternalRFQDirectCustView.wdInvokeEventHandler(InternalRFQDirectCustView.java:515)

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

at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:304)

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

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

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

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

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

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

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

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

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

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

at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)

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

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

Can anybody help me to get this resolved?

Thanks and Regards,

Nitin

[Former Member · Accepted solution]

Nitin,

Just a guess: seems that within 10 mnutes someone (re)deploys some <b>other</b> WD application but with <b>very same</b> component / controller name. Hence this error.

VS

[Former Member · Accepted solution]

Hi Valery Silaev,

Your guess is correct. my other project member having same component but namespace is different.My component getting effected when he deploys project.

Thanks for your great support.

[Former Member · Accepted solution]

Hi,

How can we resolve this problem? I have the same problem as mentionned.