Could not run WebDynpro Tutorial - NoClassDefFoundError

[Former Member]

Hallo,

I tried to develop a first WebDynpro application as it is described in the tutorial "Create a Simple WebDynpro Application". When I try to run the application the following error occurs

Web Dynpro product information:

Product: null, Vendor: SAP AG, Version: null, Build ID: 6.3003.00.0000.20031125134518.0000, Build Date: Tue Oct 05 10:47:45 CEST 2004

-

---

Error stacktrace:

java.lang.NoClassDefFoundError: com/sap/tc/webdynpro/progmodel/gci/IGCIComponentDelegate

-

---

Loader Info -

---

ClassLoader name: [local/WebDynpro_Basics]

Parent loader name: [Frame ClassLoader]

References:

service:servlet_jsp

service:ejb

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

service:jmsconnector

library:jsse

library:servlet

common:library:activation;library:mail

library:ejb20

library:j2eeca

library:jms

library:opensql

library:webservices_lib

interface:resourcecontext_api

interface:webservices

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

common:library:com.sap.security.api.sda;library:com.sap.security.core.sda;library:security.class

library:com.sap.aii.util.xml

library:tc_colapi

library:com.sap.aii.util.misc

library:tc~cmi

library:tc_colruntime

Resources:

C:\usr\sap\J2E\JC00\j2ee\cluster\server0\apps\local\WebDynpro_Basics\webdynpro\public\lib\app.jar

Loading model: {parent,references,local}

-

---

The error occurred while trying to load "com.sap.tc.webdynpro.tutorials.introduction.basics.wdp.InternalFirstComponent".

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

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

at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doInit(ClientComponent.java:738)

at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:327)

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

at com.sap.tc.webdynpro.clientserver.task.Task.createApplication(Task.java:177)

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

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

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

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:137)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:100)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:37)

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

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

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

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

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

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

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

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

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

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

I think I need a special class file in the build path, but I can not find the class which is missing in the plugins of the DeveloperStudio. Could somebody help me?

[detlev_beutner]

Hi Ebnet,

as a first question: What versions of WAS / NWDS are you using?! (Main question is if you are using corresponding versions, i.e. NWDS 2.0.x with WAS 6.40 SP x, with the same value for x.)

Hope it helps

Detlev

[Former Member]

Hi Detlev,

I tried to find out the version of the WAS, but I can't find this information. Do you know where I can look for it?

My NWDS version is 2.0.8

[Former Member]

Open http://localhost:50000/webdynpro/dispatcher/sap.com/tc_wdtools/WebDynproConsole.

Drill down to Admin Menu -> About -> Server.

Then take a look at <i>Web Dynpro Runtime Version</i> field, something like: Vendor: SAP, Build ID: 6.400<b>8</b>.XXXXX

The bolded value must correspond to the subversion of NSWD, like 2.0.<b>8</b>

Regards,

VS

[Former Member]

Thank you for your help Valery,

I found the Build ID 6.3003. Is it necessary to use WAS 6.40 for WebDynpro?

kind regards

Message was edited by: Ebnet Josef

[detlev_beutner]

Hi Ebnet,

> Is it necessary to use WAS 6.40 for WebDynpro?

No, WebDynpro works on your version, BUT: (Guaranteed) Only with NWDS 2.0.3!

So go back to the older NWDS version, if you can, or update the server to 6.40 SP8.

Hope it helps

Detlev

[Former Member]

Heck, the naming was changed (???)

Just verified: SP7 has build version 6.<u>3</u>00<b>7</b> but SP9 is 6.<u>4</u>00<b>9</b>.

Anyway, it seems that you have a mismatch: NW from SP8 and WAS from SP3. You have to use both from the same version (believe me, option with NW/WAS SP8 is muuuuch better

Regards,

VS

[Former Member]

Thanks for your help Valery and Detlev,

I will try to degrade NWDS to version 2.0.3 and hope that this will work.

kind regards

[Former Member]

Hi

I am getting an error when i map an attribute in view context to an attribute in component context .if i remove this mapping the application works fine with out the data being passed.

Error stacktrace:

<b>java.lang.NoSuchMethodError: com.sap.tc.webdynpro.progmodel.context.MappedAttribute.<init>(Lcom/sap/tc/webdynpro/progmodel/context/AttributeInfo;)V

at</b> com.sap.test.welcome.wdp.InternalStartView$ContextElement.wdpGetObject(InternalStartView.java:140)

at com.sap.tc.webdynpro.progmodel.context.AttributePointer.getObject(AttributePointer.java:140)

at com.sap.tc.webdynpro.clientserver.data.DataContainer.getAndFormat(DataContainer.java:940)

at com.sap.tc.webdynpro.clientserver.data.DataContainer.getAndFormat(DataContainer.java:917)

at com.sap.tc.webdynpro.clientimpl.csf.renderer.data.DataContainerRenderer.renderAttribute(DataContainerRenderer.java:970)

at com.sap.tc.webdynpro.clientimpl.csf.renderer.data.DataContainerRenderer.access$200(DataContainerRenderer.java:70)

at com.sap.tc.webdynpro.clientimpl.csf.renderer.data.DataContainerRenderer$AttributeRenderer.render(DataContainerRenderer.java:1225)

at com.sap.tc.webdynpro.clientimpl.csf.renderer.data.DataContainerRenderer.visitNodeOrElements(DataContainerRenderer.java:697)

at com.sap.tc.webdynpro.clientimpl.csf.renderer.data.DataContainerRenderer.visitNodeOrElements(DataContainerRenderer.java:555)

at com.sap.tc.webdynpro.clientimpl.csf.renderer.data.DataContainerRenderer.visitAttributeInfo(DataContainerRenderer.java:496)

at com.sap.tc.webdynpro.clientimpl.csf.renderer.data.DataContainerRenderer.visitNodeInfo(DataContainerRenderer.java:276)

at com.sap.tc.webdynpro.clientimpl.csf.renderer.data.DataContainerRenderer.visitContext(DataContainerRenderer.java:183)

at com.sap.tc.webdynpro.clientimpl.csf.renderer.data.DataContainerRenderer.visitDataContainer(DataContainerRenderer.java:129)

at com.sap.tc.webdynpro.clientimpl.csf.renderer.data.DataContainerRenderer.render(DataContainerRenderer.java:95)

at com.sap.tc.webdynpro.clientserver.renderer.AbstractRenderManager.render(AbstractRenderManager.java:62)

at com.sap.tc.webdynpro.clientimpl.csf.renderer.core.CSFResponseRenderer.renderDataContainerUpdates(CSFResponseRenderer.java:798)

at com.sap.tc.webdynpro.clientimpl.csf.renderer.core.CSFResponseRenderer.renderUserInterfaceUpdates(CSFResponseRenderer.java:1176)

at com.sap.tc.webdynpro.clientimpl.http.client.AbstractUpdateClientPeer.sendResponse(AbstractUpdateClientPeer.java:147)

at com.sap.tc.webdynpro.clientimpl.csf.client.CSFUpdateClientPeer.sendResponse(CSFUpdateClientPeer.java:81)

at com.sap.tc.webdynpro.clientimpl.csf.client.CSFClient.sendResponse(CSFClient.java:494)

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

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

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

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:130)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:92)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:35)

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

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

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

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

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

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

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

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

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

Is this because of the version problem.?

the NWSD Version we are using is 2.0.3

and to see the WAS version i followed the steps posted by Valery Silaev

<b>Open http://localhost:50000/webdynpro/dispatcher/sap.com/tc_wdtools/WebDynproConsole.

Drill down to Admin Menu -> About -> Server.</b>

but for us nothing is displayed in Web Dynpro Runtime Version field,

Is there any other way to see the WAS version.

If anybody has faced similar problem please do reply.

Thanks in Advance,

Lakshmi.

[Former Member]

Hi

Could anyone tell me what is the solution for this error??

thanks,

Shailaja

[Former Member]

Use compatible Web Dynpro versions in NWDS and on the Web AS.

General rule: NDWS version must not be newer than Web AS.

Armin

[Former Member]

Hi Armin,

I have NWDS 2.0.3 and Web AS 6.0.11 Let me know if this is compatible.

Thanks,

Shailaja