Brett,
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?
In wrapper style, java2wsdl assume that you already have the wrapper
classes,
if you don't have the wrapper classes, then it will generate a set of
wrapper beans for you
There's a flag you can turn on, which will compile the generated wrapper
beans,
"-classdir", just specify the location of the classdir, then the tool
knows you want to compile them.
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?
Yes, we noticed that this still not convenient, that's why we are
working on java2ws,
we hope user can just use one command and then all the things are setup
correctly, no extra steps are required.
Cheers,
James
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.
