Author: mukulg
Date: Tue Feb 1 10:09:29 2022
New Revision: 1897648
URL: http://svn.apache.org/viewvc?rev=1897648&view=rev
Log:
xercesj commit: minor improvements to xsd validation error message
Modified:
xerces/java/branches/xml-schema-1.1-dev/src/org/apache/xerces/impl/msg/XMLSchemaMessages.properties
xerces/java/trunk/src/org/apache/xerces/impl/msg/XMLSchemaMessages.properties
Modified:
xerces/java/branches/xml-schema-1.1-dev/src/org/apache/xerces/impl/msg/XMLSchemaMessages.properties
URL:
http://svn.apache.org/viewvc/xerces/java/branches/xml-schema-1.1-dev/src/org/apache/xerces/impl/msg/XMLSchemaMessages.properties?rev=1897648&r1=1897647&r2=1897648&view=diff
==============================================================================
---
xerces/java/branches/xml-schema-1.1-dev/src/org/apache/xerces/impl/msg/XMLSchemaMessages.properties
(original)
+++
xerces/java/branches/xml-schema-1.1-dev/src/org/apache/xerces/impl/msg/XMLSchemaMessages.properties
Tue Feb 1 10:09:29 2022
@@ -315,7 +315,7 @@
rcase-RecurseUnordered.2 = rcase-RecurseUnordered.2: There is not a
complete functional mapping between the particles.
# We're using sch-props-correct.2 instead of the old src-redefine.1
# src-redefine.1 = src-redefine.1: The component ''{0}'' is begin
redefined, but its corresponding component isn't in the schema document being
redefined (with namespace ''{2}''), but in a different document, with namespace
''{1}''.
- sch-props-correct.2 = sch-props-correct.2: A schema cannot contain two
global components with the same name; this schema contains two occurrences of
''{0}''.
+ sch-props-correct.2 = sch-props-correct.2: An XSD schema cannot
contain two global components with the same name. This schema contains two
occurrences of ''{0}''.
st-props-correct.1 = st-props-correct.1: ''itemType'' of xs:list and
''memberTypes'' of xs:union cannot refer to special types, xs:anyAtomicType or
xs:anySimpleType. The ''{1}'' component of simpleType ''{0}'' violates this
constraint.
st-props-correct.2 = st-props-correct.2: Circular definitions have
been detected for simple type ''{0}''. This means that ''{0}'' is contained in
its own type hierarchy, which is an error.
st-props-correct.3 = st-props-correct.3: Error for type ''{0}''. The
value of '{'final'}' of the '{'base type definition'}', ''{1}'', forbids
derivation by restriction.
Modified:
xerces/java/trunk/src/org/apache/xerces/impl/msg/XMLSchemaMessages.properties
URL:
http://svn.apache.org/viewvc/xerces/java/trunk/src/org/apache/xerces/impl/msg/XMLSchemaMessages.properties?rev=1897648&r1=1897647&r2=1897648&view=diff
==============================================================================
---
xerces/java/trunk/src/org/apache/xerces/impl/msg/XMLSchemaMessages.properties
(original)
+++
xerces/java/trunk/src/org/apache/xerces/impl/msg/XMLSchemaMessages.properties
Tue Feb 1 10:09:29 2022
@@ -274,7 +274,7 @@
rcase-RecurseUnordered.2 = rcase-RecurseUnordered.2: There is not a
complete functional mapping between the particles.
# We're using sch-props-correct.2 instead of the old src-redefine.1
# src-redefine.1 = src-redefine.1: The component ''{0}'' is begin
redefined, but its corresponding component isn't in the schema document being
redefined (with namespace ''{2}''), but in a different document, with namespace
''{1}''.
- sch-props-correct.2 = sch-props-correct.2: A schema cannot contain two
global components with the same name; this schema contains two occurrences of
''{0}''.
+ sch-props-correct.2 = sch-props-correct.2: An XSD schema cannot
contain two global components with the same name. This schema contains two
occurrences of ''{0}''.
st-props-correct.2 = st-props-correct.2: Circular definitions have
been detected for simple type ''{0}''. This means that ''{0}'' is contained in
its own type hierarchy, which is an error.
st-props-correct.3 = st-props-correct.3: Error for type ''{0}''. The
value of '{'final'}' of the '{'base type definition'}', ''{1}'', forbids
derivation by restriction.
totalDigits-valid-restriction = totalDigits-valid-restriction: In the
definition of {2}, the value ''{0}'' for the facet ''totalDigits'' is invalid,
because it must be <= the value for ''totalDigits'' which was set to ''{1}'' in
one of the ancestor types.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
