[
https://issues.apache.org/jira/browse/GEODE-6861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16875116#comment-16875116
]
ASF subversion and git services commented on GEODE-6861:
--------------------------------------------------------
Commit 2c39f92dc5fa129058144a9ec16606092dc3d51e in geode's branch
refs/heads/develop from Jinmei Liao
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=2c39f92 ]
GEODE-6861: separate static config object from runtime info in the Cl… (#3754)
Co-authored-by: Joris Melchior <[email protected]>
* use ConfigRealizer to retrieve the runtime information for configuration on
each member
* list result would return a List of Response object which has a configuration
object and a list runtime objects
* use existing object for runtime member info and move them to geode-management
module.
> 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
> 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)
