Hi, Sorry I didn't really see the replies for this mail. That's why my reply came. Ok if you have a complexed java class then what would be the easy way? I can suggest what I am doing with this.(I don't know whether it is the right method. But I used to do this) 1)generate the wsdl for your complexed class.(Java2WSDL) 2)Then using that wsdl generate the skelotons.(WSDL2Java) 3)Ok then there will be a service impl class. Fill the logics of your methods there. 4)Then fine you won't have any headaches. Deploy the service using adminclient. Everything will be fine.:)
regards, Jeyakumaran > 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 [mailto:[EMAIL PROTECTED] > Sent: 29 July 2004 15:23 > To: [EMAIL PROTECTED] > 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 > > > > Lanka Software Foundation Promoting opensource in Srilanka
