Help with DC Deployment - Cannot create delegate for component...

[tom_cole3]

I inherited a DC several months ago and have been adding functionality to it ever since. I have never had a problem compiling/deploying/executing, etc. until yesterday.

I was adding some functionality that required I add an RFC to the model (which I have done dozens of times before), etc. I had the code all ready, then I deployed and received an error message from the server that starts:

com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to create delegate for component com.linxas.applications.ofi.OFI. (Hint: Is the corresponding DC deployed correctly? Does the DC contain the component?)

I searched the forum and found several posts that talked about repairing, rebuilding, redeploying, etc. However none of those options has done anything for me. I always end up with that error.

When I do a repair on the dc, an odd thing happens. I loose reference to two variables (one is the ECLIPSE_HOME and the other is the JRE_LIB. I also loose two external jars, the ones for SapMetamodelDictionaryContent.zip and SapMetamodelWebdynproContent.zip. These four entries are missing everytime I do a repair/rebuild. I have to manually put them back.

I have tried deleting the project and reimporting, no change. I tried removing the application through VA before deploying, no change.

I get absolutely no errors in the Task panel, everything seems fine. Just to reiterate I have been working on this DC for months without a single issue. Why would the IDE just start barfing on this like that?

Any help would be greatly appreciated.

FYI, I inherited another DC at the same time and have been doing similar work on it, but have not had this problem (yet?).

Edited by: Tom Cole on Jun 3, 2009 1:44 PM

[Former Member]

Hi Tom,

Is this DC using another DC?

Check the used DCs and see if the component usage is proper.

Regards,

kartikaye

[tom_cole3]

I don't normally use DCs. I have two that I inherited from a previous coworker back in January. Both are local DCs that were converted from Web Dynpro projects. Neither use other DCs at all. To be quite hones there is no reason for them to be DCs, I just received them that way.

The two DCs look identical as far as the DC definition goes. One works, the other is giving me the error mentioned above. The DC with the problem has been functioning fine and has undergone near constant development since January. Just yesterday it started this issue.

I had deployed a version around 1:00 PM EST to send an update to the client. This worked fine as always. I then did a reimport of one of the models to add an additional RFC to it. This particular RFC is also used in dozens of other applications with no issues. After adding the RFC, I created the corresponding model node, made some minor changes to the controller (to call and use the information from the RFC) and redeployed and WHAM. That's when I had this issue.

So far I have:

Tried rebuilding/repairing/reloading and redploying, to no avail.

Tried undeploying and redeploying the dc, to no avail.

I am currently deleting the existing DC project and creating a new one with the same name, and will them attempt to put the pieces back together. I expect this will take me a very long time and I still won't know if it helps.

The other DC has continued to function as expected with no issues. It's almost like the NWDS somehow trashed my DC Definition, although a comparison shows no glaring differences with the other one that works.

[Former Member]

Hi Tom,

I would suggest you look at the build.log and the problems tab to see if there any issues.

Also, check the trace file.

There are couple of thread with the same problem check them out as well:

Regards,

Kartikaye

[tom_cole3]

Just to clarify there are no errors with this project whatsoever in the IDE. The project compiles fine and deploys without an issue. Therefore the Problems tab (Tasks on my IDE) shows all is well as does the build log.

Nothing has made even the slightest difference on the server. I still always receive the same error. Here is the entire stack trace:

com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to create delegate for component com.linxas.applications.ofi.OFI. (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.DelegatingComponent.<init>(DelegatingComponent.java:51)
	at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:381)
	at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:357)
	at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:670)
	at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:267)
	at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:706)
	at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:660)
	at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:228)
	at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
	at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:56)
	at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:40)
	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: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)
Caused by: java.lang.reflect.InvocationTargetException
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
	at com.sap.tc.webdynpro.progmodel.generation.ControllerHelper.createDelegate(ControllerHelper.java:74)
	... 27 more
Caused by: java.lang.NullPointerException
	at com.sap.tc.webdynpro.progmodel.context.NodeInfo.fillInName(NodeInfo.java:610)
	at com.sap.tc.webdynpro.progmodel.context.NodeInfo.toString(NodeInfo.java:621)
	at java.text.MessageFormat.subformat(MessageFormat.java:1230)
	at java.text.MessageFormat.format(MessageFormat.java:825)
	at java.text.Format.format(Format.java:133)
	at java.text.MessageFormat.format(MessageFormat.java:801)
	at com.sap.tc.webdynpro.services.exceptions.WDException$DummyLocalizableTextFormatter.<init>(WDException.java:71)
	at com.sap.tc.webdynpro.services.exceptions.WDRuntimeException.<init>(WDRuntimeException.java:55)
	at com.sap.tc.webdynpro.services.exceptions.WDRuntimeException.<init>(WDRuntimeException.java:48)
	at com.sap.tc.webdynpro.progmodel.context.ContextException.<init>(ContextException.java:78)
	at com.sap.tc.webdynpro.progmodel.context.NodeInfo.addItem(NodeInfo.java:291)
	at com.sap.tc.webdynpro.progmodel.context.NodeInfo.<init>(NodeInfo.java:123)
	at com.sap.tc.webdynpro.progmodel.context.DataNodeInfo.<init>(DataNodeInfo.java:74)
	at com.sap.tc.webdynpro.progmodel.context.ContextInfoFactory.createNode(ContextInfoFactory.java:32)
	at com.sap.tc.webdynpro.progmodel.gci.GCIContext.createNode(GCIContext.java:28)
	at com.linxas.applications.ofi.wdp.InternalOFI.wdCreateNodeInfos2(InternalOFI.java:3511)
	at com.linxas.applications.ofi.wdp.InternalOFI.wdCreateNodeInfos1(InternalOFI.java:3429)
	at com.linxas.applications.ofi.wdp.InternalOFI.<init>(InternalOFI.java:1811)
	... 32 more

Edited by: Tom Cole on Jun 4, 2009 1:49 PM

[Former Member]

Hi,

If possiblie, If the same NWDS is installed in another machine in your team. Can you try replace all the plugins under "IDE70\eclipse\plugins" folder with those plugins.

And Here some questions to analyze the issue:

Did you upgraded your IDE before this issue you faced? Similarly server also?

Regards,

Charan

[tom_cole3]

For those interested in what was wrong..

Somehow there was a Context Node AND a Context Attribute in the same context with the same name. How this happened I do not know, but that was the cause of the error. Changing the name of the Context Node solved the problem.

How interesting is that?

Additional Information:

Apparently the suspect node was originally created in an iView. It was later copied and pasted into the Component Controller. The paste operation did NOT determine that there was a Context Attribute that already existed with the same name and allowed the paste to continue and did not report the conflict.

Edited by: Tom Cole on Jun 4, 2009 5:49 PM

[Former Member]

Hi Tom Cole,

Did you try undeploying DC? (Using SDM -> Remote GUI)

Also check is there another application with the same name deployed on the server?

Regards,

Jaya.

[tom_cole3]

Thanks for your reponse.

I undeployed through SDM and checked for other applications with the same name, there were none.

I redeployed and still have the same error. This is very disturbing to me. Especially since the IDE shows everything as being just fine, as it has for months.

[Former Member]

Hi,

Can you delete the old application and create a new application for the same WD Component.

And check all the Interface View, Default plug exists properly.

And did you delete any objects like InterfaceView Default plug/ Existing Application/ Component/ Component Usage before this.

Regards,

Charan