Life cycle for deploying web services in axis and using them.

[Sagar Pidaparthi]

Hi,   I follow a life cycle in deploying Axis web services which looks convoluted.   Use java2wsdl get wsdls Use wsdl2java to wsdd files and proxies. Use the generated wsdd to create a deployment descriptor to be added to server-config.wsdd.  This requires quite a few changes to ensure that the service really works. Deploy and start the server Use the dynamically generated wsdl to regenerate the proxies, because the statically generated proxies can be different from dynamic ones. Then write the application using the dynamically generated proxies.   Do you follow a similar life cycle?   I feel this is somewhat convoluted.  Does any body have a simpler process?   Step 2 is needed because it provides a list of all the dependent objects needed for a service and  provides useful information for developing the deployment descriptor.  However, we are throwing away the proxies generated in step 2 and regenerating them again because wsdd  we finally use,  has been tweeked and is no longer in sync with the wsdd generated in step 2.   I know that in final stages you just use steps 5 and 6 for doing most of your application development.   I would appreciate your thoughts.   Regards   Sagar