I have used Axis/Mule and now have to work on JAXWS. When i read about it i found the steps to be 1.Write a service class. 2.Compile the Service. 3.Generate WSDL/XSD/Beans 4.Package everything. 5.Deploy(Glassfish in my case) 6.Build/Compile the client. 7.Generate the stubs. 8.Run the client.
First of all have i got the flow right? Because in Axis we developed the stubs before writing the client and that should ideally be the case.So the question is how and when are stubs used in JAXWS.
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.
Thanks peer Also, i have used ant to compile/WSDL generation/pack/deploy. You need to make the build file for ant. For Axis wsdl2java etc was much easy approach. If you could please tell me alternate approaches for compile/WSDL generation/pack/deploy.One i could think of is Eclipse plug-ins.