4

我有点重复这个问题，第一次被问错了。

我有这个：

<xsd:complexType name="A">
        <xsd:sequence>
            <xsd:element name="options" type="options"/>
        </xsd:sequence>
</xsd:complexType>

<xsd:complexType name="B">  
    <xsd:complexContent>
            <xsd:element name="options" type="ex_options"/>
    </xsd:complexContent>
</xsd:complexType>

<xsd:complexType name="options">
    <xsd:sequence>
        ...some options
    </xsd:sequence>
</xsd:element>

<xsd:complexType name="ex_options">
    <xsd:complexContent>
         <xsd:extension base="options">
             <xsd:sequence>
              ...some more options
              </xsd:sequence>
          </xsd:extension>
     </xsd:complexContent>
 </xsd:element>

所以基本上我有一个带有内部选项类的 A 类 B 类从 A 类继承，我希望 B.options 从 A.options 继承，这样当我们做 web 服务时，我们只需要传递 a 并且当我们调用 getOptions 时它会返回正确的对象 B.options。目前使用 xsd 的方式，我收到一条错误消息，指出模型组中出现了具有不同类型的名称选项的多个元素。错误属于 B 类型。

4

3 回答 3

4

只需坚持使用类型 B 的元素，然后使用适当的xsi:type属性值如下所述装饰您的实例文档元素。

<xsd:complexType name="B">  
      <xsd:complexContent>
                <xsd:element name="options" type="ex_options"/>
      </xsd:complexContent>
</xsd:complexType>

<xsd:complexType name="options">
      <xsd:sequence>
              ...some options
      </xsd:sequence>
</xsd:element>

<xsd:complexType name="ex_options">
      <xsd:complexContent>
             <xsd:extension base="options">
                   <xsd:sequence>
                        ...some more options
                    </xsd:sequence>
              </xsd:extension>
       </xsd:complexContent>
</xsd:element>

然后将您的实例元素“装饰”为

<options xsi:type="ex_options"> ...     (this will work)

或者

<options xsi:type="options"> ...     (I think you can do this as long as the base xsi:type is not abstract)

如果事实证明你不能用 base 进行装饰xsi:type，那么你总是可以通过创建一个空的 base 类型来“作弊”，然后通过仔细构造进行扩展以达到你想要的两种格式。

有关详细说明和链接，请参阅此帖子。

于 2008-11-08T04:39:23.700 回答
0

You may also use restriction rather than extension, but it is not best solution, because restriction removes all base definitions. Better case is use xsi:type at runtime (in XML instances of elements) like described in other answer.
More one example of using xsi:type is here: http://www.xfront.com/ElementHierarchy.html

<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
 <!-- Root element -->
 <xsd:element name="root" type="B"/>

 <!-- Base abstract type -->
 <xsd:complexType name="A" abstract="true">
  <xsd:sequence>
   <!-- Option that we will override -->
   <xsd:element name="options" type="options"/>
  </xsd:sequence>
 </xsd:complexType>

 <!-- Derived type -->
 <xsd:complexType name="B">
  <xsd:complexContent>
   <!--Overriding -->
   <xsd:restriction base="A">
    <xsd:sequence>
     <xsd:element name="options" type="ex_options"/>
    </xsd:sequence>
   </xsd:restriction>
  </xsd:complexContent>
 </xsd:complexType>

 <!-- Base included class -->
 <xsd:complexType name="options">
  <xsd:sequence>
   <xsd:element name="baseOption"/>
  </xsd:sequence>
 </xsd:complexType>

 <!-- Overriding of included class -->
 <xsd:complexType name="ex_options">
  <xsd:complexContent>
   <xsd:restriction base="options">
    <xsd:sequence>
     <xsd:element name="overridedOption"/>
    </xsd:sequence>
   </xsd:restriction>
  </xsd:complexContent>
 </xsd:complexType>
</xsd:schema>

In pseudo CiXML it will something like:

{
  B root;

  abstract class A
  {
    options options;
  }

  class B override A
  {
    ex_options options;
  }

  class options
  {
    empty baseOption;
  }

  class ex_option override options
  {
    empty overridedOption
  }
}

Here the example XML:

<?xml version="1.0" encoding="UTF-8"?>
<root xsi:noNamespaceSchemaLocation="polymorphism.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <options>
    <overridedOption/>
  </options>
</root>
于 2010-07-27T18:22:28.163 回答
0

您可以使options序列开放式，以便您可以拥有任意数量的选项，然后根据属性值验证现有选项。例如，在以下模式中，options列表具有type属性Aor B，指示应实际列出哪些选项：

<?xml version="1.0" encoding="utf-8" ?>
<xs:schema targetNamespace="http://tempuri.org/XMLSchema.xs"
                  elementFormDefault="qualified"
                  xmlns="http://tempuri.org/XMLSchema.xs"
                  xmlns:mstns="http://tempuri.org/XMLSchema.xs"
                  xmlns:xs="http://www.w3.org/2001/XMLSchema">

  <!-- Elements for document structure. -->
  <!-- This section is just for validating my example file to -->
  <!-- demonstrate the schema. -->
  <xs:element name="root">
    <xs:complexType>
      <xs:sequence>
        <xs:element name="elementA" type="A" minOccurs="0" maxOccurs="unbounded"/>
        <xs:element name="elementB" type="A" minOccurs="0" maxOccurs="unbounded"/>
      </xs:sequence>
    </xs:complexType>
  </xs:element>



  <!-- The important part of the schema. -->
  <!-- Types -->
  <!-- A has options of type options. -->
  <xs:complexType name="A">
    <xs:sequence>
      <xs:element name="options" type="options"/>
    </xs:sequence>
  </xs:complexType>

  <!-- Options specifies a options with a type attribute specifying which options will be available. -->
  <xs:complexType name="options">
    <xs:sequence>
      <xs:element name="option" minOccurs="0" maxOccurs="unbounded"/>
    </xs:sequence>
    <xs:attribute name="type" use="optional" default="A">
      <xs:simpleType>
        <xs:restriction base="xs:string">
          <xs:enumeration value="A"/>
          <xs:enumeration value="B"/>
        </xs:restriction>
      </xs:simpleType>
    </xs:attribute>
  </xs:complexType>

</xs:schema>

这是此模式的 XML 示例。

<?xml version="1.0" encoding="utf-8"?>
<root xmlns="http://tempuri.org/XMLSchema.xs">
  <elementA>
    <options type="A">
      <option>Test-A</option>
      <option>Test2-A</option>
    </options>
  </elementA>
  <elementB>
    <options type="B">
      <option>Test-B</option>
      <option>Test2-B</option>
      <option>Test3-B</option>
      <option>Test4-B</option>
    </options>
  </elementB>
</root>
于 2008-10-16T14:48:20.200 回答