mrglavas 2005/06/12 21:31:04
Modified: java/src/org/apache/xerces/impl/msg
XMLSchemaMessages.properties
Log:
Fixing JIRA Issue #1070:
http://issues.apache.org/jira/browse/XERCESJ-1070
The error message for maxNodeOccurs limit was misleading in
that it related the limit to the maxOccurs attribute in the
schema. It really is a limit on the number of nodes which may
be created for representing the content model of a given type.
This should be clearer now.
Revision Changes Path
1.77 +2 -2
xml-xerces/java/src/org/apache/xerces/impl/msg/XMLSchemaMessages.properties
Index: XMLSchemaMessages.properties
===================================================================
RCS file:
/home/cvs/xml-xerces/java/src/org/apache/xerces/impl/msg/XMLSchemaMessages.properties,v
retrieving revision 1.76
retrieving revision 1.77
diff -u -r1.76 -r1.77
--- XMLSchemaMessages.properties 11 May 2004 17:30:16 -0000 1.76
+++ XMLSchemaMessages.properties 13 Jun 2005 04:31:04 -0000 1.77
@@ -278,7 +278,7 @@
FacetValueFromBase = FacetValueFromBase: In the declaration of type
''{0}'', value ''{1}'' of facet ''{2}'' must be from the value space of the
base type, ''{3}''.
FixedFacetValue = FixedFacetValue: In the definition of {3}, the
value ''{1}'' for the facet ''{0}'' is invalid, because the value for ''{0}''
has been set to ''{2}'' in one of the ancestor types, and '{'fixed'}' = true.
InvalidRegex = InvalidRegex: Pattern value ''{0}'' is not a valid
regular expression. The reported error was: ''{1}''.
- maxOccurLimit = Current configuration of the parser doesn''t allow a
maxOccurs attribute value to be set greater than the value {0}.
+ maxOccurLimit = Current configuration of the parser doesn''t allow
the expansion of a content model for a complex type to contain more than {0}
nodes.
PublicSystemOnNotation = PublicSystemOnNotation: At least one of
''public'' and ''system'' must appear in element ''notation''.
SchemaLocation = SchemaLocation: schemaLocation value = ''{0}'' must
have even number of URI''s.
TargetNamespace.1 = TargetNamespace.1: Expecting namespace ''{0}'',
but the target namespace of the schema document is ''{1}''.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
