[
https://issues.apache.org/jira/browse/XERCESJ-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandy Gao resolved XERCESJ-1372.
--------------------------------
Resolution: Fixed
I went through all the schema traversing code, looking for places where we
report errors. Then I updated the schema components to make them look like they
were constructed from valid schema documents.
I try to keep the components as close to the original intent as possible, but
sometimes radical changes are necessary to make the components valid.
There are 3 kinds of errors from which I didn't try to recover: particle
restriction (complex type restriction or model group redefinition), Element
Declaration Consistent (EDC), and Unique Particle Attribution (UPA), because
- These errors are less likely to cause runtime errors (we'll see)
- It'll be difficult to recover without completely changing the content of the
complex type or group, which may produce too many validation errors.
I will soon attach a CSV file, which has details about changes I made.
> More complete recovery from schema loading errors
> -------------------------------------------------
>
> Key: XERCESJ-1372
> URL: https://issues.apache.org/jira/browse/XERCESJ-1372
> Project: Xerces2-J
> Issue Type: Improvement
> Components: XML Schema 1.0 Datatypes, XML Schema 1.0 Structures
> Affects Versions: 2.9.1
> Reporter: Sandy Gao
> Assignee: Sandy Gao
> Priority: Minor
>
> When there are errors in schema documents, we sometimes try to recover to
> make the schema still usable (to validate instance documents), but there are
> cases where we leave the schema in an inconsistent state. We should try
> harder to recover from these errors, to reduce the likelihood for exceptions
> to be thrown at runtime.
--
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]
