Class ErrorTag
java.lang.Object
org.opendaylight.yangtools.yang.common.ErrorTag
- All Implemented Interfaces:
Serializable
Extensible enumeration of
error-tag values, as defined in
RFC6241. These values are an extensible enumeration,
since YANG does not place restriction on possible values in
RFC8040.
Error tag defines overall error semantics. Additional tag-specific information may be associated with a particular error tag.
- See Also:
-
Field Summary
FieldsModifier and TypeFieldDescriptionstatic final ErrorTagaccess-deniedErrorTag.static final ErrorTagbad-attributeErrorTag.static final ErrorTagbad-elementErrorTag.static final ErrorTagdata-existsErrorTag.static final ErrorTagdata-missingErrorTag.static final ErrorTagin-useErrorTag.static final ErrorTaginvalid-valueErrorTag.static final ErrorTaglock-deniedErrorTag.static final ErrorTagunknown-elementErrorTag.static final ErrorTagmissing-attributeErrorTag.static final ErrorTagmissing-elementErrorTag.static final ErrorTagoperation-failedErrorTag.static final ErrorTagoperation-not-supportedErrorTag.static final ErrorTagDeprecated.This error-info is obsolete since RFC6241.static final ErrorTagresource-deniedErrorTag.static final ErrorTagrollback-failedErrorTag.static final ErrorTagtoo-bigErrorTag.static final ErrorTagunknown-elementErrorTag.static final ErrorTagunknown-elementErrorTag.static final ErrorTagunknown-namespaceErrorTag. -
Constructor Summary
Constructors -
Method Summary
-
Field Details
-
ACCESS_DENIED
access-deniedErrorTag. -
BAD_ATTRIBUTE
bad-attributeErrorTag. Covers mechanics specified in RFC6020 section 8.3.1, bullet 6For insert handling, if the value for the attributes "before" and "after" are not valid for the type of the appropriate key leafs, the server MUST reply with a "bad-attribute" error-tag in the rpc- error.
-
BAD_ELEMENT
bad-elementErrorTag. Covers mechanics specified in RFC6020 section 8.3.1, bullet 3If data for more than one case branch of a choice is present, the server MUST reply with a "bad-element" in the rpc-error.
-
DATA_EXISTS
data-existsErrorTag. -
DATA_MISSING
data-missingErrorTag. Covers mechanics specified in RFC6020 sections 13.5 through 13.7. -
IN_USE
in-useErrorTag. -
INVALID_VALUE
invalid-valueErrorTag. Covers mechanics specified in RFC6020 section 8.3.1, bullet 1If a leaf data value does not match the type constraints for the leaf, including those defined in the type's "range", "length", and "pattern" properties, the server MUST reply with an "invalid-value" error-tag in the rpc-error, and with the error- app-tag and error-message associated with the constraint, if any exist.
-
LOCK_DENIED
lock-deniedErrorTag. -
MALFORMED_MESSAGE
unknown-elementErrorTag. Covers mechanics specified in RFC6241, Appendix A, last item. Note the specification expressly forbids reporting this tag for NETCONF clients older than:base:1.1. -
MISSING_ATTRIBUTE
missing-attributeErrorTag. -
MISSING_ELEMENT
missing-elementErrorTag. Covers mechanics specified in RFC6020 section 8.3.1, bullet 2If all keys of a list entry are not present, the server MUST reply with a "missing-element" error-tag in the rpc-error.
as well as RFC6020 section 7.13.2, paragraph 2If a leaf in the input tree has a "mandatory" statement with the value "true", the leaf MUST be present in a NETCONF RPC invocation. Otherwise, the server MUST return a "missing-element" error.
-
OPERATION_FAILED
operation-failedErrorTag. Covers mechanics specified in RFC6020 section 13.1 through 13.4. -
OPERATION_NOT_SUPPORTED
operation-not-supportedErrorTag. -
PARTIAL_OPERATION
Deprecated.This error-info is obsolete since RFC6241.partial-operationErrorTag. -
RESOURCE_DENIED
resource-deniedErrorTag. -
ROLLBACK_FAILED
rollback-failedErrorTag. -
TOO_BIG
too-bigErrorTag. -
UNKNOWN_ATTRIBUTE
unknown-elementErrorTag. Covers mechanics specified in RFC6020 section 8.3.1, bullet 7If the attributes "before" and "after" appears in any element that is not a list whose "ordered-by" property is "user", the server MUST reply with an "unknown-attribute" error-tag in the rpc-error.
-
UNKNOWN_ELEMENT
unknown-elementErrorTag. Covers mechanics specified in RFC6020 section 8.3.1, bullet 4If data for a node tagged with "if-feature" is present, and the feature is not supported by the device, the server MUST reply with an "unknown-element" error-tag in the rpc-error.
as well as RFC6020 section 8.3.1, bullet 5If data for a node tagged with "when" is present, and the "when" condition evaluates to "false", the server MUST reply with an "unknown-element" error-tag in the rpc-error.
-
UNKNOWN_NAMESPACE
unknown-namespaceErrorTag.
-
-
Constructor Details
-
ErrorTag
-
-
Method Details