Personalize
ADS

How to edit the WSDL in a Bottom Up Web Service

Submitted by bagchijr on April 19, 2008 - 09:43. Forums :

Hello All,

 

I am relatively new at working with web services and have been programming a few sample web services that have been deployed on WSAS. However I have stumbled on a few errors in the WSDL that WSAS points out in the WSDL view. I now need to edit this WSDL so that I can program a client to call it. I am not sure how to navigate the application server to edit this WSDL file. Any suggestions would be greatly appreciated!

 

Thank you!

 

Bookmark/Search this post with:
  • Delicious
  • Digg
  • Reddit
  • Newsvine
  • Facebook
  • Google
  • Yahoo
  • Technorati
‹ Jars Specific to One Webservice? Possible to set number of retries for client stub? ›

Hi, One option would be to

Submitted by charithak on April 20, 2008 - 07:21.

Hi,

One option would be to use the wsdl validator comes with Eclipse wtp. WSAS does not provide a specific wsdl editor or validator. You can download eclipse wtp from http://www.eclipse.org/webtools/

regards

Charitha

 

»

WSDL generation

Submitted by bagchijr on April 22, 2008 - 10:42.

Hi Charitha,

Since WSAS doesn't have a WSDL editor/validator, would it be better for me to write the WSDL first and then generate Java code from it. The reason I am asking this is because I want to incorporate SOAP with attachments in the web service and the Java2WSDL generator for WSAS doesn't recognise it. At the moment I am returning a DataHandler object from the web service which WSAS is recognising as xs:anyType when I really want it to be recognised as a binary file (or xs:base64String).

Is it best to first code the WSDL and then generate Java code?

Thanks once again!

Riju

»

Whenever the tools cannot

Submitted by afkham_azeez on April 28, 2008 - 05:29.

Whenever the tools cannot handle the WSDL generation, it is always safe to hand-code the WSDL. It is sometimes difficult to map all language constructs of a programming language to WSDL. This is because the WSDL is independent of the implementation language.

 

Hence it may be prudent in you case to start with the WSDL (contract first approach)

 

 

Regards

Afkham Azeez

»

Contract First

Submitted by bagchijr on April 28, 2008 - 05:37.

Thanks Afkham,

 

I tried that as well and got confused. The WSDL generated stubs for the client. So I extended the skeleton but did not know how to deploy the service. Just need to point out I'm using Eclipse WTP, Tomcat 5.5 and Axis 2. What steps would I have to take after extending thwe skeleton to deploy the service. I have never tried the contract first approach.

 

Regards,

Riju

»