Why is Axis2 wsdl2java making this complicated of a client stub?
posted 9 years ago
I'm using the "pixie dust" approach as I hear it being called in some posts here, so maybe that is the problem, but here is what's going on...
I've deployed a simple webservice to jboss4.0.5 (with jax-ws applied) that is very simple:
On a remote server, when I build the stubs using wsdl2JAVA (based off the wsdl generated when I deploy the webservice), I seem to have to get access to the 'add result' by doing something like:
Is this normal? It seems odd to have to use an 'Add0' object and another 'Add' object that seems to wrap the Add0 object. Is there a reason the stub doesn't provide a more simple implementation (minus the seemingly pointless wrapp) like:
or even better...
The client stub generation seems overly complicated. (When I deployed the service as an RPC type the wsdl2java generated the service stub without the wrapper around the Add class.)
I can deal with it the way it is, if that's just the 'facts of life,' but I just wanted to know if I'm doing something wrong. Maybe I need to add something to the annotations?