Win a copy of Java EE 8 High Performance this week in the Java/Jakarta EE forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

Why is Axis2 wsdl2java making this complicated of a client stub?  RSS feed

Ranch Hand
Posts: 281
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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?
Always look on the bright side of life. At least this ad is really tiny:
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!