[
https://issues.apache.org/jira/browse/GEODE-389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Darrel Schneider updated GEODE-389:
-----------------------------------
Description:
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.
was:
MembershipAttributes, RequiredRoles and Roles should be deprecated and removed.
See GEODE-72.
Summary: Required Role APIs should be deprecated (was:
MembershipAttributes, RequiredRoles and Roles should be deprecated)
> Required Role APIs should be deprecated
> ---------------------------------------
>
> Key: GEODE-389
> URL: https://issues.apache.org/jira/browse/GEODE-389
> Project: Geode
> Issue Type: Wish
> Reporter: Kirk Lund
> Assignee: Kirk Lund
>
> 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)
