[NETCONF-607] RPC with no input throw NPE when called via Restconf Created: 08/Feb/19 Updated: 21/Feb/19 Resolved: 21/Feb/19 |
|
| Status: | Resolved |
| Project: | netconf |
| Component/s: | restconf-nb |
| Affects Version/s: | Neon, Fluorine SR2, Sodium |
| Fix Version/s: | Neon, Fluorine SR3, Sodium |
| Type: | Bug | Priority: | Highest |
| Reporter: | Richard Kosegi | Assignee: | Jakub Morvay |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Given RPC (no input): rpc force-refresh { when called via restconf like this: curl -u admin:admin -X POST -v http://localhost:8181/restconf/operations/jsonrpc:force-refresh Leads to following error: <html>
Karaf log indicates NPE: Caused by: java.lang.NullPointerException
Can we add check and throw RestconfDocumentedException so user will know that required input is missing? eg. this works curl -u admin:admin -X POST http://localhost:8181/restconf/operations/jsonrpc:force-refresh -d ''
|
| Comments |
| Comment by Richard Kosegi [ 08/Feb/19 ] |
|
Maybe this is regression? https://jira.opendaylight.org/browse/NETCONF-509 |