Hi Manas,
Just like Balaji, I don't think it's a good idea to publish a servlet as a webService.
A webService is a part of a business object (business rules) published to a 3rd party.
Are your business rules contained in servlets ? What about a n-tier architecture with layers ?
My understanding of the incoming
J2EE 1.4 is that we'll be able to publish a webservice from the web tier (Jax-rpc service endpoint) and the EJB tier (EJB service endpoint).
But it does not mean the web tier service has to be a servlet. Actually, it can be a POJO.
When the service is a JAX-RPC one, the WebService engine is itself a servlet. So it will meet all your security and multithreading needs.
But to answer you primary question, I think you can publish a servlet as a webservice with WSAD, because a sevlet is a class (i never tried it)
Just right click on the servlet class, and choose "Web Services / Publish as web services". Then you'll have to check the method to expose and so on so forth.