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

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

Commit 54c9300e40e465e16a827ec8b523de20b80f004f in incubator-geode's branch 
refs/heads/develop from [~bschuchardt]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=54c9300 ]

GEODE-389 Required Role APIs should be deprecated

Deprecating member-attributes and required-role in the new Geode 1.0
schema.


> Required Role APIs should be deprecated
> ---------------------------------------
>
>                 Key: GEODE-389
>                 URL: https://issues.apache.org/jira/browse/GEODE-389
>             Project: Geode
>          Issue Type: Wish
>          Components: docs, membership
>            Reporter: Kirk Lund
>            Assignee: Bruce Schuchardt
>             Fix For: 1.0.0-incubating.M2
>
>
> The following apis related to "required roles" should all be deprecated:
> - Role
> - RequiredRoles
> - MembershipAttributes
> - LossAction
> - ResumptionAction
> - RoleException
> - RegionRoleException
> - RegionAccessException
> - RegionDistributionException
> - CommitDistributionException
> - RegionRoleListener
> Methods on public APIs that use these interfaces will need to also be 
> deprecated.
> The corresponding attributes and elements in the cache xsd need to also be 
> deprecated.
> It is not clear to me what a customer using required roles can transition to. 
> Will this be a hard removal of this functionality with no alternative?
> See GEODE-72.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to