James, It also seems like I have to run java2wsdl twice, or I end up with BARE type parameters. The first time seems required to generate the wrapper classes, and once they're compiled, the second time is required to generate the WSDL. Is this correct behavior?
The first run of java2wsdl always generates lots of warnings about not being able to load the wrapper classes. But because they get compiled at the end of that phase, the second invocation of java2wsdl is able to load them. This seems strange to me. Why wouldn't a single invocation of java2wsdl generate the wrappers, compile them, and then load them to generate the WSDL file? Thanks, Brett > The reason it generate the BARE, is because the WSDL is in BARE style, > the reason WSDL is in BARE is because the java2wsdl can not load the > wrapper bean classes, > You can append the wrapper bean annotation in your SEI, so the tools > knows where to load the wrapper beans, or the tools will go to the > default location, i guess the default values is the jaxws sub-package of > the SEI package. >
