I've got a two-step mess here. First, I get the extra dimension due, presumably, to some Aegis+JAX-WS snafu. That in turn triggers a Microsoft problem.
> -----Original Message----- > From: Christopher Moesel [mailto:[EMAIL PROTECTED] > Sent: Wednesday, October 10, 2007 7:23 PM > To: cxf-user@incubator.apache.org > Subject: RE: JAX-WS+Aegis+extra array dimension > > It seems to me that maxOccurs should definitely be 1 in this case. > Perhaps that is why VS2005 is choking-- multidimensional arrays? > > I have a wsdl-first service using CXF w/JAXB and I haven't had any > problems with a VS2005 client. My WSDL does have some elements with > maxOccurs="unbounded". But I don't believe I have any 2-dimensional > arrays. > > -Chris > > -----Original Message----- > From: Benson Margulies [mailto:[EMAIL PROTECTED] > Sent: Wednesday, October 10, 2007 7:18 PM > To: cxf-user@incubator.apache.org > Subject: JAX-WS+Aegis+extra array dimension > > @WebMethod > > public abstract void addNameBatch(@WebParam(name="indexid") String > indexid, > > @WebParam(name="names")Name[] > names) throws NameIndexException; > > > > It looks to me as if an array of names has turned into an array of > arrays of names. Shouldn't naxOccurs here be 1? Or the type be a plain > Name? > > > > <xsd:element name="addNameBatch" type="tns:addNameBatch"/> > > <xsd:complexType name="addNameBatch"> > > <xsd:sequence> > > <xsd:element minOccurs="0" name="indexid" type="xsd:string"/> > > <xsd:element maxOccurs="unbounded" minOccurs="0" name="names" > type="ns1:ArrayOfName"/> > > </xsd:sequence> > > </xsd:complexType>
