You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Michael Dodge (JIRA)" <ji...@apache.org> on 2018/02/05 22:27:00 UTC

[jira] [Resolved] (GEODE-3966) PoolImpl.createAuthenticatedCacheView should not call CacheFactory.getInstance

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

Michael Dodge resolved GEODE-3966.
----------------------------------
       Resolution: Fixed
    Fix Version/s: 1.5.0

> PoolImpl.createAuthenticatedCacheView should not call CacheFactory.getInstance
> ------------------------------------------------------------------------------
>
>                 Key: GEODE-3966
>                 URL: https://issues.apache.org/jira/browse/GEODE-3966
>             Project: Geode
>          Issue Type: Sub-task
>          Components: client/server
>            Reporter: Darrel Schneider
>            Assignee: Michael Dodge
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.5.0
>
>          Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> PoolImpl.createAuthenticatedCacheView should not call CacheFactory.getInstance.
> It looks like it would be easy for all the callers of this method to pass the cache in as a parameter.
> Or maybe an InternalPool should be associated with a Cache already (there are two other uses of CacheFactory.getInstance in this class)



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