You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@jackrabbit.apache.org by "angela (JIRA)" <ji...@apache.org> on 2010/08/12 17:31:16 UTC

[jira] Created: (JCR-2713) UserManagement: Don't read cached memberships if session has pending (group) changes

UserManagement: Don't read cached memberships if session has pending (group) changes
------------------------------------------------------------------------------------

                 Key: JCR-2713
                 URL: https://issues.apache.org/jira/browse/JCR-2713
             Project: Jackrabbit Content Repository
          Issue Type: Bug
          Components: jackrabbit-core, security
            Reporter: angela
            Assignee: angela
             Fix For: 2.2.0


for backwards compatibility reasons reading group membership should not access the overall cache in case of pending (group) change.
the current implememation (always reading from cache) caused a regression in test-case we have @day that relied on accurate group
membership information with having unsaved group-member changes.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (JCR-2713) UserManagement: Don't read cached memberships if session has pending (group) changes

Posted by "angela (JIRA)" <ji...@apache.org>.

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

angela resolved JCR-2713.
-------------------------

    Resolution: Fixed

> UserManagement: Don't read cached memberships if session has pending (group) changes
> ------------------------------------------------------------------------------------
>
>                 Key: JCR-2713
>                 URL: https://issues.apache.org/jira/browse/JCR-2713
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-core, security
>            Reporter: angela
>            Assignee: angela
>             Fix For: 2.2.0
>
>
> for backwards compatibility reasons reading group membership should not access the overall cache in case of pending (group) change.
> the current implememation (always reading from cache) caused a regression in test-case we have @day that relied on accurate group
> membership information with having unsaved group-member changes.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.