[MDSAL-455] SimpleDOMActionResult should not allow empty errors with null value Created: 24/May/19 Updated: 01/Oct/19 Resolved: 01/Oct/19 |
|
| Status: | Resolved |
| Project: | mdsal |
| Component/s: | Binding API |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.0, 4.0.7 |
| Type: | Bug | Priority: | Medium |
| Reporter: | Robert Varga | Assignee: | Robert Varga |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
No return value and no errors is an violation of the intent. NETCONF is mis-representing the possiblity by throwing a runtime exception in case it cannot finish mapping - rather than creating a proper error report. |
| Comments |
| Comment by Robert Varga [ 30/Sep/19 ] |
|
I think we should add a utility static constructor, which would format an exception and produce a consistent error for the mapping case. It seems to match RFC6241 (page 80):
error-tag: malformed-message
error-type: rpc
error-severity: error
error-info: none
Description: A message could not be handled because it failed to
be parsed correctly. For example, the message is not
well-formed XML or it uses an invalid character set.
This error-tag is new in :base:1.1 and MUST NOT be
sent to old clients.
|