I'm not familiar enough with Schema to know if this is a workaround for
WSDL2Java or a problem with my Schema, but stepping through the code and
a bit of experimentation, I found that wrapping the <sequence> with
<complexContent> worked for me. e.g.

        <s:complexType>
                <s:complexContent>
                  <s:sequence>

In my case, I had a complex type with a complex content with a
restriction element (soapenc:Array) and then a sequence, but I think the
key was inserting the complexContent for reasons beyond my explanation
for now.

HTH

cheers,
        Simon

Reply via email to