WSDL problem with web dynpro dc

[Former Member]

Hello all,

I have wrestled with nasty wsdl problem for couple of days: I have a third party wsdl-file which I want to use to generate client for the web service.

Now I have tried three different approaches:

1) generate model from the wsdl in the Web Dynpro DC project I want to use the web service.

2) Use web service client that is generated for the WLS applications

3) create a DC deployable proxy and use it on the Gui DC

All of these approaches seem to fail because of the deployment or WSDL generation error.

On the first case I can't generate the proxy because I get generation error on the WSDL (I'm using adaptative web service model and local filesystem wsdl).

The second case fails because I just can't deploy the needed 3rd party jar's to the portal using Web Dynpro DC's (why this has to be so difficult? SAP please see how it's done in standard J2EE applications)

Third case is variation of the second. I can create the proxy and build my user interface DC with the WS proxy DC, but no matter what I try I run to the situation where I get java.lang.NoClassDefFoundError for the proxy class I want to use. So it seems that I can't deploy the needed proxy DC.

I would appreciate help on any of these cases.

For the background information I am using NWDS Version: 7.0.09, build id: 200608262203

BR, Janne

[Former Member]

HI Janne,

I may not have complete answer to your questions since you have not given any specific error or wsdl file.

But third party libraries can be deployed using 'External library' DC and this can be used in WD DC by declaring public parts.

( i wonder why do you need third party libraries for calling a webservice )

Hope it helps

Regards,

Arul

[Former Member]

The problem is that there isn't any specific error code. Model generator on the Netweaver dev studio just gives exception saying the generation failed when adding the operation parameters (can't check now the exact exception).

I would need 3rd party libraries since the WS interface client is built using them and will of course give ClassDefNotFoundException if I do not deploy the 3rd party jars too. I tried using External library DC to deploy the jars and everything seemed fine until I checked the deployment using SDM. Even though the deployment seems to work through the NWDS, the lib is not deployed on the J2EE engine and there's not even any error message explaining why the jars fail to deploy.

I can't understand why it has been made this difficult. Why not just give the possibility to deploy standard jars or use library paths for J2EE engine?

[Former Member]

Hi Janne,

External lib DC may not be deployed on its own. You can create a deploy time dependency when u create "used dc" relationship from webdynpro DC . This way it will both deploy the external library DC and your webdynpro.

Regards,

Arul

PS: reward points if its useful

[Former Member]

Hi,

for soap messages there are two types of styles 'rpc' and 'document'. google it to find out the difference. ABAP WAS to my knowledge interstingly supports the exposion of services both in RPC and document style but only supports creation of proxies for document style WSDLs.

regards