You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
NETCONF service provide should define more specific exceptions that reflect the different types of transport/rpc/protocol/application errors as defined in RFC 6241
Users should be able to catch more specific exceptions if desired and the exception message in any case should be human-friendly instead of direct XML output from an rpc-reply.
Steps to Reproduce
Initiate a NETCONF RPC that results in a rpc-error message.
Somewhat related to #773
Current Behavior
XML output for
rpc-error
is used as exception message. For instance:Expected Behavior
NETCONF service provide should define more specific exceptions that reflect the different types of transport/rpc/protocol/application errors as defined in RFC 6241
Users should be able to catch more specific exceptions if desired and the exception message in any case should be human-friendly instead of direct XML output from an
rpc-reply
.Steps to Reproduce
Initiate a NETCONF RPC that results in a
rpc-error
message.System Information
The text was updated successfully, but these errors were encountered: