-
Type:
Bug
-
Status: Resolved
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 7.10
-
Component/s: Core
The bug is visible when two fields are based on complex whose simple element has the same name, for instance value in the below XSD definiton
<xs:element name="country" type="nxs:smt_country"/> <xs:complexType name="smt_country"> <xs:sequence> <xs:element name="value"> <xs:simpleType> <xs:restriction base="xs:string" ref:resolver="directoryResolver" ref:directory="country"/> </xs:simpleType> </xs:element> </xs:sequence> </xs:complexType> <xs:element name="language" type="nxs:smt_language"/> <xs:complexType name="smt_language"> <xs:sequence> <xs:element name="value"> <xs:simpleType> <xs:restriction base="xs:string" ref:resolver="directoryResolver" ref:directory="language"/> </xs:simpleType> </xs:element> </xs:sequence> </xs:complexType>
After selecting a value for both fields and submitting the form, there will be a validation error
"zh" is not a valid country id
which is inconsistent because the second field use languages, not countries.
The problem may be when the fields are registered after loading the XSD contributions
- is required by
-
NXP-27847 Undeprecate some XSDLoader methods
-
- Resolved
-
