axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roy, Anthony" <>
Subject RE: WSDD and WSDL
Date Fri, 30 Jul 2004 08:08:18 GMT
I am fairly new to axis and WSDL/WSDD, but there seems to me two ways to go
about setting up a web service with the three technologies axis, WSDL and

1) Create the Java classes to act as your web service. Create a WSDD to
deploy the classes as a web service on Axis. Use Java2WSDL or the axis
application manager to generate the WSDL file. Use the WSDL file to generate
client stubs to do the bulk of the work involved in calling the web service.

2) Create a WSDL file describing what you want your web service to do. Use
WSDL2Java to generate the Client stubs, the Service skeleton and the WSDD
files for deploying and undeploying the application. Pad out the skeleton
and stubs to make it do what you want.

Pro's and con's of the approaches? From what I have seen so far, the former
is good if you already have a web service that just needs deploying, since
WSDD files are pretty easy to write, and your java classes are already
created. You can automatically generate the WSDL in order to provide a way
of easily generating clients for the service. This is also the easiest way
if you have no experience of WSDL, as you can use the generated WSDL as a
template for future applications using the second method.

The latter is probably the better approach if you do not already have a web
service in place, but you have a good idea of what you want the service to
look like. You then build up a single WSDL file which can then do most of
the work for you, and provides a single point of maintenance (well, more
than that really, since you need to maintain the skeleton override class
that does the actual work).


Anthony Roy.

t: 01937 54 (6003)

> -----Original Message-----
> From: Suzy Fynes [] 
> Sent: 29 July 2004 15:32
> To:; 'Anand Natrajan'
> Subject: RE: WSDD and WSDL
> That's a big help! Thanks!
> Just one other thing, if I have a more complicated java class 
> that I wish to deploy as a web service, does that mean I use 
> a wsdd file to deploy it?If so where does the wsdl come from?
> -----Original Message-----
> From: Anand Natrajan [] 
> Sent: 29 July 2004 15:23
> To:
> Subject: Re: WSDD and WSDL
> Suzy,
> WSDDs are Axis artifacts - they're present just to tell Axis 
> what service you intend deploying. Subsequent to deploying a 
> WSDD you have a web service (running inside Axis), and can 
> get to the service's WSDL.
> JWS files also are Axis artifacts, I believe (this one I not 
> so sure about). If you have really simple webservices, then 
> you can get around the long process (write a java interface, 
> java2wsdl it to get a WSDL, wsdl2java the WSDL to get server 
> skeletons and a WSDD file) and simply deploy the JWS file 
> instead. It's a quickie web service straight from your Java 
> code. Doesn't work for complex types though. Again, once you 
> have deployed a JWS file, you have a web service (again 
> running inside Axis), and you can get to the service's WSDL.
> As a radically different example, if you were in the .NET 
> world and wanted to deploy a service inside IIS, you wouldn't 
> have WSDDs and JWS files. Instead, you'd write a 
> C#/J#/VB/VC++ class, tag the class as a WebService, tag some 
> methods as WebMethods and then turn on the .NET blender. At 
> the end of it, you'd get a deployable executable. Running 
> that simply installs your web service (running inside IIS 
> this time). After that, consult your friendly IIS manual to 
> figure out how to get the WSDL for the service.
> Hope that made a few things clearer.
> Anand
> On Thu, 29 Jul 2004, Suzy Fynes wrote:
> : I'm just looking for clarity as to exactly how the web service
> : deployment descriptor works.  How is it interrelated with 
> wsdl in axis?
> : Do I still create the WSDL by deploying a jws file? Once 
> tested using
> : the AdminClient class in axis how is processed from there?
> :
> : Any help would be great!
> : Thanks,
> : Suzy


Experience the British Library online at 

Help the British Library conserve the world's knowledge. Adopt a Book. 


The information contained in this e-mail is confidential and may be legally
privileged. It is intended for the addressee(s) only. If you are not the
intended recipient, please delete this e-mail and notify the : The contents of this e-mail must not be disclosed or
copied without the sender's consent. 

The statements and opinions expressed in this message are those of the
author and do not necessarily reflect those of the British Library. The
British Library does not take any responsibility for the views of the


View raw message