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
