Welcome WD Application - Exception

[Former Member]

Hi

I tried to write my first WD application, like it is described in the online help. (I mean the Welcome Application with only two views, where you can enter your name in the first view and it is displayed in the second view). I'm using 6.30 and Nw Developer Studio 2.04.

I did no coding at all !! (everything was declarative), and I get a NoSuchMethodError from the Reflection API.

Any Ideas what's missing? I guess something with my Context is not ok. I defined just a simple value attribute as described in the online help.

Raphael

com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: failed to created delegate

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

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)

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.DelegatingComponent.<init>(DelegatingComponent.java:42)

... 26 more

Caused by: java.lang.NoSuchMethodError: com.sap.tc.webdynpro.progmodel.context.Context.createAttribute(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;ZZ)Lcom/sap/tc/webdynpro/progmodel/context/AttributeInfo;

at com.sap.training.wd.welcome.wdp.InternalWelcomeComponent.<init>(InternalWelcomeComponent.java:43)

... 31 more

-

---

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.DelegatingComponent.<init>(DelegatingComponent.java:42)

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)

Caused by: java.lang.NoSuchMethodError: com.sap.tc.webdynpro.progmodel.context.Context.createAttribute(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;ZZ)Lcom/sap/tc/webdynpro/progmodel/context/AttributeInfo;

at com.sap.training.wd.welcome.wdp.InternalWelcomeComponent.<init>(InternalWelcomeComponent.java:43)

... 31 more

[kevin_mao]

Dear all,

I met the same exception when I try the example dynpro application. The installed softwares are "Sneak Preview Edition Web Application Server Java 6.40" and "SAP NetWeaver Developer Studio 2.0.7" ( checked the help document of studio 2.0.7, the platform 6.40 should be compatible.

And I try to import the example code package into studio and the same exception was met.

Any help?

Regards,

Kevin

[Former Member]

Hi Kevin,

i guess, there is a mismatch between the build libraries you are using at design time in the Developer Studio and the runtime libraries the server uses. The generated classes call method(s) which aren't anymore or not yet available on the server. This is the reason why the IDE and server patch levels must be the same. It doesn't matter, if you use prebuilt example projects or create the projects by yourself, since the classes will be regenerated before you can deploy.

Since you are using 2.0.7 DevStudio, there should be something like a Support Package 07 WebAS available for you. The Sneak preview downloadable is definitely NOT compatible with a .7 NDS.

Hope that helps.

Regards

Stefan

[Former Member]

Hi all,

this whole mess is caused be the fact that in 6.30 there was only one Install for the DevStudio and the LocalEngine (DevleoperWorkplace). With 6.40 you have to apply one patch to your NWDS and another to your local Server. This fundamental change was not communicated at all. It would be great the 6.30-proceeding could be reestablished

Regards

Michael Barth

[Former Member]

Hi Michael,

or, much more easier NDS should <b>reject</b> deploying on a server which hasn't a patch level which isn't compatible with the own one.

Best regards

Stefan

[Former Member]

Hi Stefan,

very good proposal. Today we have a SAP-Consultant here at our office. I'll give him that input for future releases.

Regards

Michael

[Former Member]

Hi Raphael,

Please send me your project.

Best regards, Karin

[Former Member]

I'm experiencing exactly the same problem as Raphael. Is there any Web Dynpro Runtime configuration needed before you can run the Web Dynpro application? I'm working with Web AS 6.40 and NDS 2.0.5.. The J2EE applications are running fine.

Best regards,

Daniela

[Former Member]

Hi Daniela,

no, there are no special WD configuration steps necessary in general. Please post the exception here.

Best regards

Stefan

[Former Member]

Hi Stefan!

Here is the exception:

com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: failed to created delegate

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

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)

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.DelegatingComponent.<init>(DelegatingComponent.java:42)

... 26 more

Caused by: java.lang.NoSuchMethodError: com.sap.tc.webdynpro.progmodel.context.Context.createAttribute(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;ZZ)Lcom/sap/tc/webdynpro/progmodel/context/AttributeInfo;

at com.sap.examples.welcome.wdp.InternalWelcomeComponent.<init>(InternalWelcomeComponent.java:43)

... 31 more

-

---

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.DelegatingComponent.<init>(DelegatingComponent.java:42)

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)

Caused by: java.lang.NoSuchMethodError: com.sap.tc.webdynpro.progmodel.context.Context.createAttribute(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;ZZ)Lcom/sap/tc/webdynpro/progmodel/context/AttributeInfo;

at com.sap.examples.welcome.wdp.InternalWelcomeComponent.<init>(InternalWelcomeComponent.java:43)

... 31 more

Best regards,

Daniela

[Former Member]

Hi Daniela,

looking at the package names i guess you used the Welcome example project delivered with the Developer Studio? Or did you try to build it step by step from the tutorial in the docs? I imported it right now and it runs as it is, so if you created the project by yourself, please test the prebuilt project first.

Best regards,

Stefan

[Former Member]

Hi Stefan,

I already tried both methods , via the tutorial docs and then I experimented with the prebuilt projects, but none of them run succesfully. Even the other examples (WebDynpro_Quiz and so) didn't run properly. Do you have another hint where I can look?

I have to say that I had to uninstall and install the Web AS 6.40, because the J2EE Server was continously stopping.

Maybe I did not clear something properly ?

How could I test if my Web Dynpro environment is ok?

Kind regards,

Daniela

[Former Member]

Hi Daniela,

that doesn't sound good really. Let's try one of the prebuilt WD applications. Please enter the url: http://<yourhost>:50000/webdynpro/welcome and login as Administrator at the "Content Administrator" or the "Web Dynpro Console".

Best regards,

Stefan

[Former Member]

Hi Daniela,

Could it be possible that you have the installation runing 90 days already? After 90 days the licence is not valid anymore and the engine stops after 30 min.

Hope that helps!

Karin

[Former Member]

Hi Stefan !

When I try to Run as Preview in the Content Administrator I get the same exception. Do I need to configure SLD before running Web Dynpros?

What else can I test?

Kind regards,

Daniela

[Former Member]

Hi Karin!

No this was not the problem. Nevertheless I solved this problem already, the problem now is that I get an exepction when trying to run Web Dynpros, similar to what Rafael had. Could you give some hints about this problem?

Best Regards,

Daniela

[Former Member]

Hi Daniela,

no, you don't need the SLD for running them in general. Since you were able to start the content admin, WD runtime seems to be ok (the content admin itself is a WD app, which wouldn't run otherwise).

Next try: Please build a completely new WD project. After finishing the project wizard, add an application and try to deploy and start this.

Best regards,

Stefan

[Former Member]

Hi Stefan !

Sorry I got the same error! Could it be useful to clear some data? Or would it make sense to undeploy certain SDA files or to deploy additional files???

Daniela

[Former Member]

Hi Daniela,

really strange. You don't have to deploy or undeploy SDAs normally (it's not easy anyway, since they have to be deployed in the correct order). After the WAS installation and if the deployment works using SDM (starting from the Developer Studio) you should be able to use Web Dynpro out of the box.

I guess, you restarted the server more than once in the meantime? I you've done so and it still fails, there might have been a problem again during the installation.

I'm running out of ideas, has somebody else an idea?

Best regards

Stefan

[Former Member]

Hi,

I followed this thread quite interested, since we have the very same exception with WebAS 6.40 SP4.

The Welcome app or some projects I migrated from 6.30 throw the exception. The rest is the same as with Daniela and Raphael. In fact we have this exception on 2 developer workplaces.

Interesting: The exception is only thrown when I deploy on my local Server (DeveloperWorkplace). When I deploy the same project on our Standalone Server it works fine.

Regards

Michael

Message was edited by: Michael Barth

[Former Member]

Hi Daniela,

It is quite complicated to reproduce this error. I remember that I had the same kind of error if I did the uninstallation with a newer version than I used for the first installation. Could it be that case? If so, the machine then could have some files left which belongs to another version and causes this error.

If so, please install the Sneak Preview on a another machine again, where you did not install a Web AS version before and try again.

Hope that helps!

Karin

[Former Member]

Hi Karin,

at least for us this is not the case.

We uninstalled the J2EE-Engine with the uninstsap.exe from c:\usr\sap\<sid>\jc00

and the Developer with the JDTsetup.exe from the 6.30 CD we received from SAP.

A file JDTSetup.exe was not on our filesystem (as described in Migration Guide 6.30/6.40 on page 3). So we used the one from the CD

Regards

Michael

[Former Member]

Hello,

although the NWDS 2.0.5 install docs give no hint, it is necessary to upgrade your 6.30 J2EE engine to SP05 as well. Note 657763 has the solution.

cheers

Walter

[Former Member]

Hello Walter,

If you install Sneak Preview II you have a working and tested J2EE and the appropriate IDE. On the other hand - It would be interested for me where you got SP05 from? I thought that this would be only available for ramp-up customers...

Thanks alot, Karin

[Former Member]

Hello Karin,

I am a RampUp customer, I see others here and I am willing to help.

And everyone who had installed sneak preview II (containing NWDS 2.0.4) and got the RampUp DVDs (containing NWDS 2.0.3) will want to upgrade to SP5 (containing NWDS 2.0.5); at the speed we are working here, downgrading is not an option.

greetings

Walter

[Former Member]

Hi Walter,

You are right. Not every IDE works with every Engine. So if you upgrade you should upgrade the whole package. If you want to use a different IDE version and you are not sure, if it works with the engine or not, you could install the IDE in addition and test it. If it works, just delete the "older" IDE. If it does not work, you know that you have to upgrade the Engine as well.

And another tip: If you would like to run parallel IDEs please delete the following files from here:

C:\Windows\SAPwksta\sapwksta.xml and sapwksta.bak

Hope that is useful. Thanks Walter!

Best regards,

Karin