geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Owen Nichols (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (GEODE-7024) CMS Java API on locator and client should have similar error handling
Date Thu, 01 Aug 2019 15:41:00 GMT

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

Owen Nichols resolved GEODE-7024.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 1.10.0

> 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
>             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
(v7.6.14#76016)

Mime
View raw message