geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GEODE-6861) generify ClusterManagementService APIs
Date Mon, 01 Jul 2019 21:09:00 GMT

    [ https://issues.apache.org/jira/browse/GEODE-6861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16876500#comment-16876500
] 

ASF subversion and git services commented on GEODE-6861:
--------------------------------------------------------

Commit 0fa422b9981d222eb32b51af880140a2ed151da0 in geode's branch refs/heads/feature/GEODE-6930
from Jinmei Liao
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=0fa422b ]

GEODE-6861: class renaming (#3758)

* rename RespondsWith to CorrespondsWith
* rename Response to ConfgiurationResult (as opposed to RealizationResult)
* further type ConfigurationRealizer


> generify ClusterManagementService APIs
> --------------------------------------
>
>                 Key: GEODE-6861
>                 URL: https://issues.apache.org/jira/browse/GEODE-6861
>             Project: Geode
>          Issue Type: Improvement
>          Components: management
>            Reporter: Owen Nichols
>            Assignee: Jinmei Liao
>            Priority: Major
>             Fix For: 1.10.0
>
>          Time Spent: 8h 20m
>  Remaining Estimate: 0h
>
> currently CMS calls like `list(CacheElement)` return `<? extends RuntimeCacheElement>`
which then has to be cast to the appropriate actual type.
> if we create a link between the filter type and result type, then generics can be used
to give the correct actual return type in all cases, and we can get rid of a ton of warnings
and sketchy workarounds like passing `class` parameters to methods that shouldn't need them.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message