[jira] [Assigned] (GEODE-7024) CMS Java API on locator and client should have similar error handling

["Jinmei Liao (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/GEODE-7024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jinmei Liao reassigned GEODE-7024:
----------------------------------

    Assignee: Jinmei Liao  (was: Owen Nichols)

> 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: Jinmei Liao
>            Priority: Major
>             Fix For: 1.10.0
>
>          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
(v8.3.4#803005)