I should also mention that given the same WSDL file, .NET's "wsdl.exe"
utility generates an implementation that doesn't use any wrapper classes in
the operation definitions.
- Ryan
-----Original Message-----
From: Ryan LeCompte [mailto:ryan.lecompte_at_pangonetworks.com]
Sent: Wednesday, November 03, 2004 11:37 AM
To: 'users_at_jax-rpc.dev.java.net'
Subject: RE: Generated wrapper classes for document style web services
Doug,
I've tried passing the -f:unwrap option along with -f:wsi and
-f:documentliteral, but it still generates the wrapper classes.
-- Ryan
-----Original Message-----
From: Doug Kohlert [mailto:Doug.Kohlert_at_Sun.COM]
Sent: Wednesday, November 03, 2004 11:41 AM
To: users_at_jax-rpc.dev.java.net
Subject: Re: Generated wrapper classes for document style web services
This was done to behave more like .Net. Try adding the -f:unwrap option to
wscompile.
Ryan LeCompte wrote:
> Hello all,
>
> When going from a document style WSDL file to Java interfaces, I
> notice that the generated endpoint Java interface uses "wrapper"
> arguments instead of the original types defined in the WSDL. The
> wscompile command that I'm using is:
>
>wscompile -gen:server -model model -f:wsi -f:documentliteral -keep -s
>generated -d output/server -classpath . config.xml
>
>
>
>When I provide my "servant" implementation of the generated interface,
>I have to actually use the getXXX() methods
>
>on the generated wrapper classes to get at the underlying data structures
(an array of X objects, for example).
>
>
>
>Why are the wrapper classes needed when -f:wsi is specified?
>
>
>
>-- Ryan
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_jax-rpc.dev.java.net
For additional commands, e-mail: users-help_at_jax-rpc.dev.java.net
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_jax-rpc.dev.java.net
For additional commands, e-mail: users-help_at_jax-rpc.dev.java.net