Hi, I really need some guidance here. I'm creating a web service from a legacy distributed interface. My legacy code already has a complex package structure and we have automated build scripts based on that structure. In the Userguide, you explain how to use Java2WSDL to create a wsdl file, then WSDL2Java to create the bindings. Works fine, *but*...
WSDL2Java helpfully generates type mapping classes from the WSDL. The problem is that it assigns each type class to the package in which the original class is located so after it runs there are *two* FooData.java classes in the same package (the original class and the type class). Clearly, this won't work with my legacy code base! What I need to have happen is to have WSDL2Java place the type mapping class in a custom package. I can't figure out how to tell it to do this or even how to hand edit the wsdl file derived from the legacy interface via Java2WSDL. Is this a bug in WSDL2java? This sort of problem doesn't arise in your AddressBook example because WSDL2Java isn't used in the example scenario to create the wsdl file in the directory -- no original classes exist in the package before the wsdl file is created. You don't have an example of my use scenario in which there already exist some classes and I'm using the legacy info to define the web service interface (the wsdl file is generated from Java2WSDL). I suspect that my problem will be common as web services make it into the mainstream. At least one other person following your mailing lists also has this issue. I'd really, really appreciate some help here -- a tip, a pointer to an example, anything you could spare. TIA, Sheri [EMAIL PROTECTED]
