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 even nicer if the DII stuff could do this. i.e. remove the layers of complex type wrapping and just accept of Vector of concrete types to "marshal" into the operation 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 Matthew > -----Original Message----- > From: Olivier Brand [mailto:[EMAIL PROTECTED]] > 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 @yahoo.com address at http://mail.yahoo.com >
