https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/CONTROLLER-461 controller <p><a href="https://jira.opendaylight.org/browse/CONTROLLER-177" title="Fix netconf exception handling" class="issue-link" data-issue-key="CONTROLLER-177"><del>CONTROLLER-177</del></a> (Fix netconf exception handling) added the NetconfDocumentedException to the checkSuccessReply method. However the method still throws an IllegalStateException internally (i.e. it does not use the added exception as well).</p> <p>This bug should modify the method to throw the proper NetconfDocumentedException (since it is required for proper downstream handling of netconf related errors).</p> <p>Operating System: Mac OS<br/> Platform: PC</p> CONTROLLER-461

NetconfMapping.checkSuccessReply(NetconfMessage) should throw NetconfDocumentedException

Bug Resolved Done Tom Pantelis Devin Avery Thu, 8 May 2014 15:02:00 +0000 Thu, 19 Jun 2014 12:27:11 +0000 Thu, 19 Jun 2014 12:27:11 +0000 Helium netconf 0 4 <p>There already is an RpcError class containing the necessary info to produce appropriate restconf error output. Instead of setting an exception in the Future, I think NetconfDeviceListener.processMessage should convert the NetconfDocumentedException into an RpcError and return an RpcResult in the Future. I think this is the intention of the invoke RPC interface – an exception should only be thrown as a result of drastic internal error, ie unchecked ex (eg NPE) in code. It should make every effort to return an RpcError.</p> <p>Submitted: <a href="https://git.opendaylight.org/gerrit/#/c/7608/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/7608/</a></p> Development External issue ID 977 External issue URL Rank 0|i02kjj: