You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Michael Engelhart <me...@mac.com> on 2004/05/17 19:52:07 UTC
wsdl2java and .NET WSDL file
Hi -
First off I'm new to WebServices although I've successfully built an
application that uses a WS from a WSDL document and wsdl2java included
in Axis.
That said, I am working with a vendor that has multiple services
available through Web Services. They have documentation on using Axis
so I went and ran wsdl2java for a single service to see what the
classes looked like. Lo and behold this single service generated over
300 classes! Is it just me or is that out of control? The developers
said that in .NET it just generates a single file but in Java it
generates this many classes.
I just can't wrap my head around how each call to this service can
generate 300 objects per request or maybe I'm misunderstanding
something.
Any advice would be appreciated.
Thanks
Mike
Re: wsdl2java and .NET WSDL file
Posted by James Black <jb...@ieee.org>.
Michael Engelhart wrote:
> Hi -
>
> First off I'm new to WebServices although I've successfully built an
> application that uses a WS from a WSDL document and wsdl2java included
> in Axis.
>
> That said, I am working with a vendor that has multiple services
> available through Web Services. They have documentation on using
> Axis so I went and ran wsdl2java for a single service to see what the
> classes looked like. Lo and behold this single service generated
> over 300 classes! Is it just me or is that out of control? The
> developers said that in .NET it just generates a single file but in
> Java it generates this many classes.
> I just can't wrap my head around how each call to this service can
> generate 300 objects per request or maybe I'm misunderstanding something.
If they are passing many objects back and forth to the webservice,
this will create a large number of classes. Most of these should just
be simple beans with getters and setters, so it shouldn't require you to
understand them any more than knowing which getter/setter to call.
Each public class in java is it's own file, that is not the case in .net.
--
"Love is mutual self-giving that ends in self-recovery." Fulton Sheen
James Black james@usf.edu