Reimporting the WSDL file

[Former Member]

Hi all,

We are doing a scenario in which we are connecting to the ABAP and Areba systems by means of XI publishing it as Web Services and getting the WSDL file .Then we are importing the WSDL file into the webdynpro project .The question is if there is any change in the XI server it will reflect in the WSDL file .Then the file has to be reimported. Is there any way to avoid manually reimporting the file from the webdynpro program ?For example when we are changing the server from development to production .

Regards

Rohit

[Former Member · Accepted solution]

Hi Rohit,

Independent of if you use a web service model in web dynpro or a deployable or standalone proxy, you always have to regenerate your proxy if the wsdl changes. You have to check your code which uses the proxy anyway, because the signatures of the methods might have changed.

best regards,

Martin

[Former Member · Accepted solution]

hi ,

what we want to do is to avoid going to code level modifications using Netweaver Development Studio. We are developing it as an Application Package,so that it can be implemented by external manipulations of files and without altering the code.

Any ideas

Regards

Rohit

[Former Member · Accepted solution]

Rohit, Did you ever find an answer to the question about

re-importing when going from dev to prod? I am using a

standalone proxy, but have the exact same problem.

Regards

[Former Member · Accepted solution]

I have an answer, sort of, at least for anyone using the

standalone proxy. Navigate to Web Services Container

in Visual Administrator and create the library jar in

the proxy tab. Still need to figure out an elegant way

of going from the jar file to an SDA without using

NetWeaver Studio.

Anyway, the .sda can be uploaded using the SDM tool.

The client which might be a servlet or an iView would

then simply use the sda library.