[
https://issues.apache.org/jira/browse/GEODE-7024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16897743#comment-16897743
]
ASF subversion and git services commented on GEODE-7024:
--------------------------------------------------------
Commit e2855b4d2359c8a7f402f8dbd011292645b94b5a in geode's branch
refs/heads/develop from Owen Nichols
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=e2855b4 ]
GEODE-7024: raise a Java exception on non-success response from REST API (#3861)
* GEODE-7024: raise a Java exception on non-success response from REST call
> CMS Java API on locator and client should have similar error handling
> ---------------------------------------------------------------------
>
> Key: GEODE-7024
> URL: https://issues.apache.org/jira/browse/GEODE-7024
> Project: Geode
> Issue Type: Improvement
> Components: management
> Reporter: Owen Nichols
> Assignee: Owen Nichols
> Priority: Major
> Time Spent: 3h 20m
> Remaining Estimate: 0h
>
> The two implementations of ClusterManagementService should behave similarly
> in how errors are handled. Currently calls to ClientClusterManagementService
> return a ClusterManagementResult bearing the status of the call, while calls
> to LocatorClusterManagementService are declared to return the same status
> wrapper, but in fact may often throw a Java exception instead.
> The goal is to be able to code to the ClusterManagementService interface.
> Therefore to be consistent, ClientClusterManagementService should be changed
> to raise error statuses as Java exceptions, just as a Java developer would
> expect.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
