-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Anup,
If .jws is sufficient for you (you're using simple types such as strings, ints and arrays) then fine. You don't need to do anything further - the WSDL comes in potentially when writing clients and not, in this case, the server.
The WSDL informs the client software (or its author) how it, he or she should interact with the service. In the case of .jws deployment you don't need to explicitly save or generate this, it will be available at the ?wsdl address. For example, if your service endpoint is at http://foo.com/myservice.jws the WSDL will be available at http://foo.com/myservice.jws?wsdl
On the client side I suggest you take a look at http://ws.apache.org/axis/java/user-guide.html especially the section 'Using WSDL with Axis' (it's a bit over half way down) which explains the use of the WSDL2Java tool to build your client side stubs. A stub class is a bit of code that abstracts away the transport (SOAP + HTTP) from the client code, and it is this code that can be generated automatically from the WSDL.
HTH,
Tom -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (Cygwin32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFAqMlFvIo3NIa9d1ARAm85AJ4jc59E2mgljD+vLr0/qXJudoc0mwCfVSIw GnbER9fQBcZF5yDH9EfhnjA= =fOc4 -----END PGP SIGNATURE-----
