Originally posted by Mustafa Garhi:
Because in Axis we developed the stubs before writing the client and that should ideally be the case.
That is still the case under JAX-WS - however the client application probably has a larger purpose than just accessing the service, so "client application development" could be started before the stubs are available.
I would like to point out that the development that you describe is called "contract last" development. Contract last development is usually chosen for "developer convenience".
For a variety of reasons, optimizing client interoperability being one of them,
contract first web service development should be the preferred method.
Bottom-up or Top-down Starting Out Webservice - WSDL or Java Class JAX-RPC to JAX-WS (Client impact) A simple example of JAX-WS contract last development which uses
wsgen. For contract first development the service skeleton is generated with
wsimport (
Creating a service from WSDL).
[ December 04, 2008: Message edited by: Peer Reynders ]