if you do not bother about the wrapper elements do somthing like this,
<xsd:element name="getVisiblePortfoliosResponse"
type="txsns:ArrayOfCardinisPortfoliosType" />
On Nov 14, 2007 1:33 PM, Mauro Molinari <[EMAIL PROTECTED]> wrote:
> Amila Suriarachchi ha scritto:
> > On Nov 13, 2007 7:01 PM, Mauro Molinari <[EMAIL PROTECTED]> wrote:
> > Here is the response element for this operation
> >
> > <xsd:element name="getVisiblePortfoliosResponse">
> > <xsd:complexType>
> > <xsd:sequence>
> > <xsd:element name="visiblePortfolios"
> > type="txsns:ArrayOfCardinisPortfoliosType">
> > </xsd:element>
> > </xsd:sequence>
> > </xsd:complexType>
> > </xsd:element>
> >
> > the unwrapping basically happens in one level. So the generated
> > method should take the visiblePortfolios as an argument.
> > For return types this happen only if inner complex type has one
> > element.
>
> Hi Amila,
> actually this is exactly the case: the visiblePortfolios element has
> just one element, an array of CardinisPortfoliosType in this case!
> In fact, the generated wrapper class ArrayOfCardinisPortfoliosType has
> an only "useful" method, getItem(), that returns that array ("item" is
> the name of the element in the ArrayOfCardinisPortfoliosType complex
> type definition). But WSDL2Java does not do the unwrapping.
>
> Do you suggest any other way to define and array in a document/literal
> wrapped style WSDL so that WSDL2Java can do the unwrapping?
>
> It would be VERY helpful, because working with these wrappers makes the
> code quite unconfortable to manage...
>
> --
>
> Mauro Molinari
> Software Developer
> [EMAIL PROTECTED]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Amila Suriarachchi,
WSO2 Inc.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
