Incorrect error location information in errors that are detected after the
initial schema parse (e.g., UPA errors)
------------------------------------------------------------------------------------------------------------------
Key: XERCESC-1820
URL: https://issues.apache.org/jira/browse/XERCESC-1820
Project: Xerces-C++
Issue Type: Bug
Components: Validating Parser (XML Schema)
Affects Versions: 2.8.0, 3.0.0
Reporter: Boris Kolpackov
Errors that are checked for after the initial schema parser (see call to
preContentValidate()) are reported with incorrect file name and line/column
information. If the schema is loaded via schemaLocation attribute then the
error points to the schemaLocation attribute in the XML file itself, for
example:
Error at file /tmp/test.xml, line 3, char 44
Message: complex type 'type' violates the unique particle attribution rule in
its components '##any' and 'bar'
When the schema is loaded via loadGrammar(), the file name and line/column
information is not provided at all.
I guess to be able to fix this bug we will first need to add the
file/line/column information to the SchemaGrammar when it is produced by the
TraverseSchema object.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
