Uploaded image for project: 'Nuxeo Studio'
  1. Nuxeo Studio
  2. NXS-2441

Use an xsd file with a custom date type creates a string field

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Duplicate
    • Affects Version/s: 22.1
    • Fix Version/s: None
    • Component/s: Documents
    • Tags:
    • Sprint:
      Sprint io 7.1-7, Sprint io 7.2-2, NOS 10.2.3
    • Story Points:
      0

      Description

      I want to deploy a .xsd which contains constraint rules. The goal is to use the "import" feature of Studio, so "the resulting Nuxeo schema will be readonly and the XSD file will be deployed as is into the Nuxeo Repository".

      The problem is: My .xsd file is not correctly passed/imported by Studio. I have one single field (event21century), which should ultimately be a date but it displays as a string. here is the xsd:

      <?xml version="1.0" encoding="UTF-8"?>
      <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:nxs="http://www.nuxeo.org/ecm/project/schemas/My/Super/GreatSchema" targetNamespace="http://www.nuxeo.org/ecm/project/schemas/My/Super/GreatSchema">
        <xs:simpleType name="type_event21century">
          <xs:restriction base="xs:date">
            <xs:minInclusive value="2001-01-01"/>
            <xs:maxInclusive value="2100-12-31"/>
          </xs:restriction>
        </xs:simpleType>  
      
        <xs:element name="event21century" type="nxs:type_event21century"/>
      </xs:schema>
      

      See "CreatedStringField.png", it creates a String field instead.
      Or am I missing something in the xsd declaration maybe?

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: