I'm looking for guidance in using Java2WSDL and WSDL2Java together.
This seems like a common scenario. I've got a normal Java class that implements a service called CarQuote. It has a getQuote method that accepts a Car parameter. I've also got the Car class that holds the make, model, year and color of a car. Assume I can't use JWS because I know I want to use a custom type mapping later.
I'd like to deploy CarQuote as a web service.
I use Java2WSDL to generate a WSDL description of CarQuote.
Then I use WSDL2Java to generate CarQuoteService.java, CarQuoteServiceLocator.java, CarQuoteSoapBindingImpl.java, CarQuoteSoapBindingSkeleton.java, CarQuoteSoapBindingStub.java, deploy.wsdd and undeploy.wsdd.
The problem is that WSDL2Java also generates a new Car class and an interface called CarQuote. Both of these overwrite the existing .java files.
Is it common to use both Java2WSDL and WSDL2Java this way?
If so, what's the recommendation for avoiding overwriting the files?
I could rename them and name them back after WSDL2Java runs.
It seems like WSDL2Java should have an option to tell it not to overwrite existing files.
***************************************************************************************
WARNING: All e-mail sent to and from this address will be received or
otherwise recorded by the A.G. Edwards corporate e-mail system and is
subject to archival, monitoring or review by, and/or disclosure to,
someone other than the recipient.
***************************************************************************************
