Skip to content

Commit

Permalink
Revert change in SchemaException handling
Browse files Browse the repository at this point in the history
The change switched SchemaException in connectors from FATAL to
PARTIAL, but also silenced SchemaException occurring in the model.
Tests like TestPreviewChanges and TestMapping then failed, as they
didn't get expected SchemaException's.

So reverting that change now.
  • Loading branch information
mederly committed Aug 30, 2018
1 parent c26caf3 commit f064e78
Showing 1 changed file with 1 addition and 1 deletion.
Expand Up @@ -674,7 +674,7 @@ public static void handleConnectorErrorCriticality(ResourceType resourceType, Th
} else {
ErrorSelectorType errorSelector = ResourceTypeUtil.getConnectorErrorCriticality(resourceType);
if (errorSelector == null) {
if (e instanceof CommunicationException || e instanceof SchemaException) {
if (e instanceof CommunicationException) {
// Just continue evaluation. The error is recorded in the result.
// The consistency mechanism has (most likely) already done the best.
// We cannot do any better.
Expand Down

0 comments on commit f064e78

Please sign in to comment.