Is the package structure created when running WSDL2Java entirely at the mercy of the value of the targetNamespace attribute in the definitions tag? If targetNamespace is (for example) http://www.mycorp.com/wsdl/MyServices.wsdl, the package structure for the binding and service becomes com.mycorp.www.wsdl.MyServices_wsdl. Meanwhile, along with
<soap:address location="http://localhost:8080/axis/services/MyProduct"/> in the <services> part of the WSDL file, I get the file com/mycorp/services.java Is there any way to change the class structure generated by WSDL2Java?
