There follows the solution of the problem for anyone interested. The problem manifested when using more than one array properties of the same type. It was due to a change made to the default handling of collections, which previously used a wrapper element around the collection but now does not. You should be able to change the default handling by passing --wrap-collections=true on the command line.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dennis Sosnoski Sent: Tuesday, July 24, 2007 2:39 PM To: JiBX users Subject: Re: [jibx-users] jibx2wsdl: wrong schema generated Hi Pavel, I tried duplicating your problem, using an IStar interface (with name and index number) and changing the Dvd class and the hd.IDvd interface in example4 to use an IStar[]. This seems essentially the same as what you describe (an interface with methods accepting/returning an array of instances of another interface), but I wasn't able to recreate the problem. Can you try modifying one of the examples to demonstrate the problem, and send me that? Thanks, - Dennis Dennis M. Sosnoski SOA and Web Services in Java Training and Consulting http://www.sosnoski.com - http://www.sosnoski.co.nz Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117 Pavel Sharov wrote: > Dennis, > > I can now see that it always happens with arrays of complex types. Maybe > it can help you before I have to send you the whole project, I still > hope there's no need to. > For example: > > // my service > public interface IRemoteRepoService > { > IProjectDTO getProject(String projectName); > } > > // DTO > public interface IProjectDTO > { > IProjectDTOComponent[] getCntDescriptions(); > > void setCntDescriptions(IProjectDTOComponent[] comps); > } > > // DTO component > public interface IProjectDTOComponent > { > String getRawContent(); > void setRawContent(String content); > } > > // schema generated with the previous version of jibx2wsdl > <xsd:complexType name="IProjectDTOComponent"> > <xsd:sequence> > <xsd:element type="xsd:string" name="rawContent" minOccurs="0"/> > </xsd:sequence> > </xsd:complexType> > <xsd:complexType name="IProjectDTO"> > <xsd:element name="cntDescriptions" minOccurs="0"> > <xsd:complexType> > <xsd:sequence> > <xsd:element type="tns:IProjectDTOComponent" > name="cntDescription" minOccurs="0" maxOccurs="unbounded"/> > </xsd:sequence> > </xsd:complexType> > </xsd:element> > </xsd:complexType> > > // schema generated with the current version of jibx2wsdl > <xsd:complexType name="IProjectDTOComponent"> > <xsd:sequence> > <xsd:element type="xsd:string" name="rawContent" minOccurs="0"/> > </xsd:sequence> > </xsd:complexType> > <xsd:element ref="tns:IProjectDTOComponent" minOccurs="0" > maxOccurs="unbounded"/> > > Pavel > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Dennis > Sosnoski > Sent: Tuesday, July 24, 2007 1:19 AM > To: JiBX users > Subject: Re: [jibx-users] jibx2wsdl: wrong schema generated > > Hi Pavel, > > Sure looks like a bug to me. :-) Can you send me (directly) your > project, so I can investigate both this and the other issue for myself? > > Thanks, > > - Dennis > > Dennis M. Sosnoski > SOA and Web Services in Java > Training and Consulting > http://www.sosnoski.com - http://www.sosnoski.co.nz > Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117 > > > > Pavel Sharov wrote: > >> Dennis, >> >> Using the updated version of the Jibx2Wsdl I am having a problem with >> the schema generated along with the WSDL file for my service. The >> > schema > >> is imported by the generated WSDL and contains description of my DTO >> complex object. Now the complex type definition contains sequence of >> equal incomplete elements (fragment follows): >> >> <xsd:complexType name="IProjectDTO"> >> <xsd:sequence> >> <xsd:element ref="tns:IProjectDTOComponent" minOccurs="0"/> >> <xsd:element ref="tns:IProjectDTOComponent" minOccurs="0"/> >> <xsd:element ref="tns:IProjectDTOComponent" minOccurs="0"/> >> <xsd:element ref="tns:IProjectDTOComponent" minOccurs="0"/> >> <xsd:element ref="tns:IProjectDTOComponent" minOccurs="0" >> maxOccurs="unbounded"/> >> <xsd:element ref="tns:IProjectDTOComponent" minOccurs="0" >> maxOccurs="unbounded"/> >> <xsd:element ref="tns:IProjectDTOComponent" minOccurs="0" >> maxOccurs="unbounded"/> >> <xsd:element ref="tns:IProjectDTOComponent" minOccurs="0" >> maxOccurs="unbounded"/> >> <xsd:element ref="tns:IProjectDTOComponent" minOccurs="0" >> maxOccurs="unbounded"/> >> <xsd:element ref="tns:IProjectDTOComponent" minOccurs="0" >> maxOccurs="unbounded"/> >> <xsd:element ref="tns:IProjectDTOComponent" minOccurs="0" >> maxOccurs="unbounded"/> >> <xsd:element ref="tns:IProjectDTOComponent" minOccurs="0" >> maxOccurs="unbounded"/> >> <xsd:element ref="tns:IProjectDTOComponent" minOccurs="0" >> maxOccurs="unbounded"/> >> <xsd:element ref="tns:IProjectDTOComponent" minOccurs="0" >> maxOccurs="unbounded"/> >> </xsd:sequence> >> </xsd:complexType> >> >> With the previous version of the framework I had for the same complex >> type the following: >> >> <xsd:complexType name="IProjectDTO"> >> <xsd:sequence> >> <xsd:element type="tns:IProjectDTOComponent" name="routeTable" >> minOccurs="0"/> >> <xsd:element name="mapDescriptions" minOccurs="0"> >> <xsd:complexType> >> <xsd:sequence> >> <xsd:element type="tns:IProjectDTOComponent" >> name="mapDescription" minOccurs="0" maxOccurs="unbounded"/> >> </xsd:sequence> >> </xsd:complexType> >> </xsd:element> >> <xsd:element name="xltProcDescriptions" minOccurs="0"> >> <xsd:complexType> >> <xsd:sequence> >> <xsd:element type="tns:IProjectDTOComponent" >> name="xltProcDescription" minOccurs="0" maxOccurs="unbounded"/> >> </xsd:sequence> >> </xsd:complexType> >> </xsd:element> >> <xsd:element type="tns:IProjectDTOComponent" >> > name="serverOptions" > >> minOccurs="0"/> >> <xsd:element name="XMLSchemas" minOccurs="0"> >> <xsd:complexType> >> <xsd:sequence> >> <xsd:element type="tns:IProjectDTOComponent" >> name="XMLSchema" minOccurs="0" maxOccurs="unbounded"/> >> </xsd:sequence> >> </xsd:complexType> >> </xsd:element> >> <xsd:element name="testMessageDescriptions" minOccurs="0"> >> <xsd:complexType> >> <xsd:sequence> >> <xsd:element type="tns:IProjectDTOComponent" >> name="testMessageDescription" minOccurs="0" maxOccurs="unbounded"/> >> </xsd:sequence> >> </xsd:complexType> >> </xsd:element> >> <xsd:element name="xltDescriptions" minOccurs="0"> >> <xsd:complexType> >> <xsd:sequence> >> <xsd:element type="tns:IProjectDTOComponent" >> name="xltDescription" minOccurs="0" maxOccurs="unbounded"/> >> </xsd:sequence> >> </xsd:complexType> >> </xsd:element> >> <xsd:element name="BXltDescriptions" minOccurs="0"> >> <xsd:complexType> >> <xsd:sequence> >> <xsd:element type="tns:IProjectDTOComponent" >> name="BXltDescription" minOccurs="0" maxOccurs="unbounded"/> >> </xsd:sequence> >> </xsd:complexType> >> </xsd:element> >> <xsd:element name="HL7Segments" minOccurs="0"> >> <xsd:complexType> >> <xsd:sequence> >> <xsd:element type="tns:IProjectDTOComponent" >> name="HL7Segment" minOccurs="0" maxOccurs="unbounded"/> >> </xsd:sequence> >> </xsd:complexType> >> </xsd:element> >> <xsd:element type="tns:IProjectDTOComponent" name="logActions" >> minOccurs="0"/> >> <xsd:element name="XMLStyleSheets" minOccurs="0"> >> <xsd:complexType> >> <xsd:sequence> >> <xsd:element type="tns:IProjectDTOComponent" >> name="XMLStyleSheet" minOccurs="0" maxOccurs="unbounded"/> >> </xsd:sequence> >> </xsd:complexType> >> </xsd:element> >> <xsd:element name="cntDescriptions" minOccurs="0"> >> <xsd:complexType> >> <xsd:sequence> >> <xsd:element type="tns:IProjectDTOComponent" >> name="cntDescription" minOccurs="0" maxOccurs="unbounded"/> >> </xsd:sequence> >> </xsd:complexType> >> </xsd:element> >> <xsd:element name="messageDescriptions" minOccurs="0"> >> <xsd:complexType> >> <xsd:sequence> >> <xsd:element type="tns:IProjectDTOComponent" >> name="messageDescription" minOccurs="0" maxOccurs="unbounded"/> >> </xsd:sequence> >> </xsd:complexType> >> </xsd:element> >> <xsd:element type="tns:IProjectDTOComponent" >> > name="syntaxVersion" > >> minOccurs="0"/> >> </xsd:sequence> >> </xsd:complexType> >> >> Is that a bug? If needed, I could provide more info and data. >> Thank you! >> >> Pavel >> >> >> > ------------------------------------------------------------------------ > - > >> This SF.net email is sponsored by: Splunk Inc. >> Still grepping through log files to find problems? Stop. >> Now Search log events and configuration files using AJAX and a >> > browser. > >> Download your FREE copy of Splunk now >> http://get.splunk.com/ >> _______________________________________________ >> jibx-users mailing list >> jibx-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/jibx-users >> >> >> > > ------------------------------------------------------------------------ > - > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > jibx-users mailing list > jibx-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jibx-users > > ------------------------------------------------------------------------ - > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > jibx-users mailing list > jibx-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jibx-users > > ------------------------------------------------------------------------ - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ jibx-users mailing list jibx-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jibx-users ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ jibx-users mailing list jibx-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jibx-users
