[
https://issues.apache.org/jira/browse/GEODE-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16334820#comment-16334820
]
ASF subversion and git services commented on GEODE-3554:
--------------------------------------------------------
Commit ec53f620359f85b4d3c0063b34ec5911e84c50c9 in geode's branch
refs/heads/develop from [~agingade]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=ec53f62 ]
GEODE-3554: Add additional javadoc about how to get Cache.
> Document not invoking CacheFactory.getAnyInstance() from user callbacks
> -----------------------------------------------------------------------
>
> Key: GEODE-3554
> URL: https://issues.apache.org/jira/browse/GEODE-3554
> Project: Geode
> Issue Type: New Feature
> Components: core
> Reporter: Fred Krone
> Assignee: Anilkumar Gingade
> Priority: Major
> Labels: cache, geode-150, pull-request-available
>
> As long as the product continues to invoke user plug-in callbacks during
> startup (and with the main thread), we probably need to document a warning
> not to use CacheFactory.getAnyInstance() as the API call is common in
> plug-ins and this will freeze startup.
> We are planning on deprecating and removing CacheFactory.getAnyInstance()
> anyway.
> Documentation should recommend using preferred APIs:
> * FunctionContext.getCache()
> * Event.getRegion().getCache()
> We could expose Event.getCache() to make it more obvious to users.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
