axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Russell Butek" <>
Subject RE: Using DII with complex types ??
Date Wed, 06 Feb 2002 13:40:38 GMT
Be careful with this statement of removing layers.  That's not strictly
true.  When the binding uses document literal we remove a layer (I think we
do that because .NET does it).  When the binding uses rpc encoding we do
not remove the layer.

As long as you construct classes for complexTypes properly you  can use
them in the DII model.  You have to do everything yourself in DII, that's
the drawback to 'dynamic', it doesn't help you.  Or are you saying you wish
the Call object had methods with which you could construct a complex
parameter bit by bit?  That would be difficult.

Russell Butek

"J. Matthew Pryor" <> on 02/05/2002 08:10:52 PM

Please respond to

To:   <>
Subject:  RE: Using DII with complex types ??

This is an interesting question

If you look at how the stub emitter currently works (well the CVS version I
have), it actually "removes" layers from complex types, so if you have
operation that takes as a parameter a complex type with a single xsd:string
element with minoccurs & maxoccurs = 1, the stub generates a method with a
java.lang.String parameter

Now this is very nice because it make the stub easy to use. It would be
nicer if the DII stuff could do this. i.e. remove the layers of complex
wrapping and just accept of Vector of concrete types to "marshal" into the

However I guess the issue is that this does not conform literally to the
WSDL. I personally think it would be nice to support both

a) a literal mapping
b) a easy to use mapping that just accepted the raw data and took care of
the details


> -----Original Message-----
> From: Olivier Brand []
> Sent: Monday, February 04, 2002 10:01 PM
> To: axis
> Subject: Using DII with complex types ??
> Just wondering if it makes sense to use the JAX-RPC DII feature when the
> operation is dealing with complex types ?
> I believe the DII feature is to avoid manual stub generation. But you
> still need to deal with complex types if any.
> What do you have to do on the client side (the caller) in order to
> manipulate complex types ??
> Olivier
> _________________________________________________________
> Do You Yahoo!?
> Get your free address at

View raw message