Author: mukulg
Date: Wed Sep 25 04:51:20 2019
New Revision: 1867505
URL: http://svn.apache.org/viewvc?rev=1867505&view=rev
Log:
minor improvements to space character at end-of-line in xsd error messages.
this issue is not present on trunk.
Modified:
xerces/java/branches/xml-schema-1.1-dev/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=1867505&r1=1867504&r2=1867505&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
Wed Sep 25 04:51:20 2019
@@ -44,7 +44,7 @@
KeyRefOutOfScope = Identity Constraint error: the keyref identity
constraint \"{0}\" refers to a key or unique that is out of scope.
KeyRefReferNotFound = Key reference declaration \"{0}\" refers to
unknown key with name \"{1}\".
UnknownField = Internal identity constraint error; unknown field
\"{0}\" for identity constraint \"{2}\" specified for element \"{1}\".
- ## KeyRefNotEnoughValues = cvc-identity-constraint.4.3.b: Not enough
values specified for <keyref name=\"{1}\"> identity constraint specified for
element \"{0}\".
+ ## KeyRefNotEnoughValues = cvc-identity-constraint.4.3.b: Not enough
values specified for <keyref name=\"{1}\"> identity constraint specified for
element \"{0}\".
# Ideally, we should only use the following error keys, not the ones under
# "Identity constraints". And we should cover all of the following errors.
@@ -128,7 +128,7 @@
src-attribute.5 = src-attribute.5: The property ''fixed'' is present
in attribute ''{0}'', so the value of ''use'' must not be ''prohibited''.
src-attribute.6.2 = src-attribute.6.2: Since attribute ''{0}''
contains the 'targetNamespace' attribute, the 'form' attribute must be absent.
src-attribute.6.3.1 = src-attribute.6.3.1: Since attribute ''{0}''
contains the 'targetNamespace' attribute and <schema> does not have a
'targetNamespace' attribute or its value is different from the value of
'targetNamespace' of ''{0}'', ''{0}'' must have a <complexType> as an ancestor.
- src-attribute.6.3.2 = src-attribute.6.3.2: Since attribute ''{0}''
contains the 'targetNamespace' attribute and <schema> does not have a
'targetNamespace' attribute or its value is different from the value of
'targetNamespace' of ''{0}'', there must be a <restriction> ancestor between
''{0}'' and the nearest <complexType> ancestor, and the value of the 'base'
attribute of <restriction> does not match the name of 'xs:anyType'.
+ src-attribute.6.3.2 = src-attribute.6.3.2: Since attribute ''{0}''
contains the 'targetNamespace' attribute and <schema> does not have a
'targetNamespace' attribute or its value is different from the value of
'targetNamespace' of ''{0}'', there must be a <restriction> ancestor between
''{0}'' and the nearest <complexType> ancestor, and the value of the 'base'
attribute of <restriction> does not match the name of 'xs:anyType'.
src-attribute_group.2 = src-attribute_group.2: The intersection of
wildcards is not expressible for attribute group ''{0}''.
src-attribute_group.3 = src-attribute_group.3: Circular definitions
detected for attribute group ''{0}''. Recursively following attribute group
references eventually leads back to itself.
src-ct.1 = src-ct.1: Complex Type Definition Representation Error for
type ''{0}''. When <complexContent> is used, the base type must be a
complexType. ''{1}'' is a simpleType.
@@ -315,7 +315,7 @@
# 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}''.
- 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.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.
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.
@@ -326,8 +326,8 @@
minScale-totalDigits = minScale-totalDigits: In the definition
of {2}, value of minScale = ''{0}'' must be <= value of maxScale = ''{1}''.
cvc-maxScale-valid = cvc-maxScale-valid: For type {2}, and
value {0}, it is an error for the value of precision ''{3}'' to be greater than
the value of maxScale ''{1}''.
- cvc-minScale-valid = cvc-minScale-valid: For type {2}, and
value {0}, it is an error for the value of precision ''{3}'' to be less than
the value of minScale ''{1}''.
- cvc-explicitTimezone-valid = cvc-explicitTimezone-valid: Value
''{0}'' is not facet-valid with respect to explicitTimezone ''{1}'' for type
''{2}''.
+ cvc-minScale-valid = cvc-minScale-valid: For type {2}, and
value {0}, it is an error for the value of precision ''{3}'' to be less than
the value of minScale ''{1}''.
+ cvc-explicitTimezone-valid = cvc-explicitTimezone-valid: Value
''{0}'' is not facet-valid with respect to explicitTimezone ''{1}'' for type
''{2}''.
maxScale-valid-restriction = maxScale-valid-restriction: In the
definition of {2}, maxScale value = ''{0}'' must be <= that of the base type
''{1}''.
minScale-valid-restriction = minScale-valid-restriction: In the
definition of {2}, minScale value = ''{0}'' must be >= that of the base type
''{1}''.
timezone-valid-restriction = timezone-valid-restriction: In the
definition of {0}, the value ''{1}'' for the facet ''explicitTimezone'' is
invalid, because the value for ''explicitTimezone'' has been set to ''{2}'' in
one of the ancestor types.
@@ -354,7 +354,7 @@
c-general-xpath-ns = c-general-xpath-ns: A namespace prefix in XPath
expression ''{0}'' was not bound to a namespace.
c-cta-xpath = c-cta-xpath: The XPath expression ''{0}'' couldn''t
compile successfully in ''{1}'' mode, during CTA evaluation.
c-cta-xpath-b = c-cta-xpath-b: The CTA XPath expression such as
(''{0}'') containing / or //, while in ''{1}'' mode, cannot yield a valid
result (since a CTA tree is rooted at a parentless element).
- c-cta-xpath-serr = c-cta-xpath-serr: The XPath expression ''{0}''
couldn''t compile successfully in ''{1}'' mode, during CTA evaluation. A static
error ''{2}'' occured in the XPath expression.
+ c-cta-xpath-serr = c-cta-xpath-serr: The XPath expression ''{0}''
couldn''t compile successfully in ''{1}'' mode, during CTA evaluation. A static
error ''{2}'' occured in the XPath expression.
c-selector-xpath = c-selector-xpath: The selector value = ''{0}'' is
not valid; selector xpaths cannot contain attributes.
EmptyTargetNamespace = EmptyTargetNamespace: In schema document
''{0}'', the value of the ''targetNamespace'' attribute cannot be an empty
string.
FacetValueFromBase = FacetValueFromBase: In the declaration of type
''{0}'', value ''{1}'' of facet ''{2}'' must be from the value space of the
base type, ''{3}''.
@@ -367,7 +367,7 @@
TargetNamespace.2 = TargetNamespace.2: Expecting no namespace, but the
schema document has a target namespace of ''{1}''.
UndeclaredEntity = UndeclaredEntity: Entity ''{0}'' is not declared.
UndeclaredPrefix = UndeclaredPrefix: Cannot resolve ''{0}'' as a
QName: the prefix ''{1}'' is not declared.
- FacetsContradict = FacetsContradict: For simpleType definition
''{2}'', the enumeration value ''{0}'' contradicts with value of ''{1}'' facet.
+ FacetsContradict = FacetsContradict: For simpleType definition
''{2}'', the enumeration value ''{0}'' contradicts with value of ''{1}'' facet.
# JAXP 1.2 schema source property errors
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
