Details
-
Improvement
-
Status: In Progress
-
Medium
-
Resolution: Unresolved
-
None
Description
RestconfDocumentedException has a number of problems:
- it is tied to WebApplicationException, which is a JAX-RS thing
- it requires status, which is a JAX-RS thing
- if can be instantiated with no errors
- it is an unchecked exception
- it's instantiation is quite verbose for users
Gradually address all of these issues. The primary goal is to ditch the binding to JAX-RS. In that regard the actual status code should always be inferred from the error list.
Attachments
Gerrit Reviews
| # | Subject | Branch | Project | Status | CR | V |
|---|---|---|---|---|---|---|
| 108579,1 | WIP: Prototype restconf.common.errors.ErrorPath | master | netconf | Status: NEW | 0 | -1 |
| 108580,8 | WIP: Add RequestFuture | master | netconf | Status: NEW | 0 | -1 |
| 109147,3 | WIP: RestconfDocumentException should be checked | master | netconf | Status: NEW | 0 | -1 |