[YANGTOOLS-1023] Clean up yang.common.RpcError interface Created: 30/Aug/19  Updated: 19/Sep/23

Status: Confirmed
Project: yangtools
Component/s: None
Affects Version/s: None
Fix Version/s: 14.0.0

Type: Epic Priority: High
Reporter: Robert Varga Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Epic Name: Usable RpcError

 Description   

RpcError is a historic attempt at reporting errors across NETCONF-like boundaries and Java. Unfortunately it has the major flaws of

  • not doing anything for error-path
  • not doing the right thing for error-tag (i.e. an extensible enumeration)
  • ALL YOUR more-info ARE BELONGS TO java.lang.String

We need a better replacement and transition to it.

 Comments   
Comment by Robert Varga [ 30/Aug/19 ]

Note current implementations should remain as externalizable proxies, so that the serialization format does not change.

Comment by Robert Varga [ 30/Aug/19 ]

... which probably is not feasible anyway, as RpcResult has an unknown type of value (different between binding and DOM) and RpcError has a wrong definition of getInfo(), which again needs to be specialized between binding and DOM.

Generated at Wed Feb 07 20:54:58 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.