users@jax-rpc.java.net

Re: Generated wrapper classes for document style web services

From: Doug Kohlert <Doug.Kohlert_at_Sun.COM>
Date: Wed, 03 Nov 2004 08:40:35 -0800

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