mirror of
https://github.com/projectacrn/acrn-hypervisor.git
synced 2025-04-30 12:44:07 +00:00
5fcb58a4b2
Today we are using, in the configurator, the complete scenario XML schema to validate XML files given by users. While this helps identify invalid XMLs at an early stage, such checks are too strict because the configurator users may save invalid XMLs if they keep some errors in the forms unresolved, and we do allow them to save anytime they want. As a result, users may save something that they cannot load back anymore. This patch introduces a tailored version of the scenario XML schema which only verifies the existence of the top-level nodes that the configurator assumes to exist. This seems to be a good balance that blocks XMLs that are broken or using old formats but permits those that has local and fixable data issues. Tracked-On: #6691 Signed-off-by: Junjie Mao <junjie.mao@intel.com>
28 lines
1.1 KiB
XML
28 lines
1.1 KiB
XML
<?xml version="1.0"?>
|
|
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
|
|
<!-- This is a tailored version of the schema of scenario XML files and is used by the configurator to ensure files
|
|
from users have the basic structure of a valid scenario XML. We do not use the full-fledged schema here because
|
|
users are allowed to save a scenario XML with some data inconsistencies. -->
|
|
<xs:element name="acrn-config">
|
|
<xs:complexType>
|
|
<xs:all>
|
|
<xs:element name="hv">
|
|
<xs:complexType>
|
|
<xs:all>
|
|
<xs:any maxOccurs="unbounded" processContents="skip" />
|
|
</xs:all>
|
|
</xs:complexType>
|
|
</xs:element>
|
|
<xs:element name="vm" minOccurs="0" maxOccurs="unbounded">
|
|
<xs:complexType>
|
|
<xs:all>
|
|
<xs:element name="load_order" type="xs:string" />
|
|
<xs:any maxOccurs="unbounded" processContents="skip" />
|
|
</xs:all>
|
|
<xs:attribute name="id" type="xs:integer" />
|
|
</xs:complexType>
|
|
</xs:element>
|
|
</xs:all>
|
|
</xs:complexType>
|
|
</xs:element>
|
|
</xs:schema> |