BUG - Nuxeo Studio generating syntactically invalid schema for nested complex types

[russtrotter_]

Hello, I'm noticing that if you create a schema in Nuxeo Studio with the advanced config option "allow nested complex types", then actually create nested complex types, the XSD that gets generated is syntactically incorrect. Here's a snippet of the XSD that gets generated:

<xs:complexType name="glanswer_answersType">
<xs:sequence>
  <xs:element name="answerContent" type="xs:string"/>
  <xs:element name="properties" type="nxs:glanswer_propertiesListType"/>
  <xs:complexType name="glanswer_propertiesListType">
    <xs:sequence>
      <xs:element name="item" type="nxs:glanswer_propertiesType" minOccurs="0" maxOccurs="unbounded"/>
    </xs:sequence>
  </xs:complexType>
  <xs:complexType name="glanswer_propertiesType">
    <xs:sequence>
      <xs:element name="name" type="xs:string"/>
      <xs:element name="value" type="xs:string"/>
    </xs:sequence>
  </xs:complexType>
</xs:sequence>

</xs:complexType>

Notice the <xs:complexType> nested which XSD doesn't allow. As it stands now, i have to manually edit the schema as a workaround.

I'm observing this behavior on Nuxeo Studio 2.15 on my DM 5.8-HF01

thanks

[russtrotter_]

This isn't really a full answer, but it's an acceptable workaround. I still think the underlying issue is a bug in studio.

After I "Update" from "Update Center" to pull down the latest studio stuff, I do the following:

• edit offending schema that get unpacked from the studio bundle in nxserver/schemas directory, fix busted syntax
• in studio, delete the GUI-created schemas
• create new schemas with the same name/prefix as the originals, but use the Advanced option to "Import" an XSD
• Upload the edited schema

When you next run the update, Nuxeo DM reinitializes correctly, and no errors processing the schema.

[Anahide_Tchertc]

Hi,

[russtrotter_]

Ok, here's what I did (all within studio)

[Anahide_Tchertc]

Thanks a lot for the report and the detailed steps to reproduce!

[russtrotter_]

Thanks for the update! My user creds don't have access to the NXS jira space, so i might just have to keep my fingers crossed

[Anahide_Tchertc]

Ah ok, i thought it was public, i'll look into it

[Anahide_Tchertc]

Hi,

[Anahide_Tchertc]

Hi,

The corresponding bug (https://jira.nuxeo.com/browse/NXS-1851) is now fixed, thanks again for the report and the steps to reproduce.