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/01/06 17:48:00 UTC

[jira] Created: (JCR-2452) DefaultPrincipalProvider#collectGroupMembership puts wrong principal instance into the cache

DefaultPrincipalProvider#collectGroupMembership puts wrong principal instance into the cache
--------------------------------------------------------------------------------------------

                 Key: JCR-2452
                 URL: https://issues.apache.org/jira/browse/JCR-2452
             Project: Jackrabbit Content Repository
          Issue Type: Bug
          Components: jackrabbit-core
    Affects Versions: 2.0-beta4
            Reporter: angela
            Assignee: angela
             Fix For: 2.0-beta5, 2.0.0


DefaultPrincipalProvider#collectGroupMembership adds the passed principal instance to the cache. This may cause
inconsistencies as the cache should only contain principals obtained from by the provider.

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


[jira] Updated: (JCR-2452) DefaultPrincipalProvider#collectGroupMembership puts wrong principal instance into the cache

Posted by "Marcel Reutegger (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/JCR-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marcel Reutegger updated JCR-2452:
----------------------------------

    Fix Version/s:     (was: 2.0-beta5)

> DefaultPrincipalProvider#collectGroupMembership puts wrong principal instance into the cache
> --------------------------------------------------------------------------------------------
>
>                 Key: JCR-2452
>                 URL: https://issues.apache.org/jira/browse/JCR-2452
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-core
>    Affects Versions: 2.0-beta4
>            Reporter: angela
>            Assignee: angela
>             Fix For: 2.0.0
>
>
> DefaultPrincipalProvider#collectGroupMembership adds the passed principal instance to the cache. This may cause
> inconsistencies as the cache should only contain principals obtained from by the provider.

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


[jira] Updated: (JCR-2452) DefaultPrincipalProvider#collectGroupMembership puts wrong principal instance into the cache

Posted by "Marcel Reutegger (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/JCR-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marcel Reutegger updated JCR-2452:
----------------------------------

    Fix Version/s: 2.1.0

Merged into 2.0 branch in revision: 896793

> DefaultPrincipalProvider#collectGroupMembership puts wrong principal instance into the cache
> --------------------------------------------------------------------------------------------
>
>                 Key: JCR-2452
>                 URL: https://issues.apache.org/jira/browse/JCR-2452
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-core
>    Affects Versions: 2.0-beta4
>            Reporter: angela
>            Assignee: angela
>             Fix For: 2.0.0, 2.1.0
>
>
> DefaultPrincipalProvider#collectGroupMembership adds the passed principal instance to the cache. This may cause
> inconsistencies as the cache should only contain principals obtained from by the provider.

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


[jira] Resolved: (JCR-2452) DefaultPrincipalProvider#collectGroupMembership puts wrong principal instance into the cache

Posted by "angela (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/JCR-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

angela resolved JCR-2452.
-------------------------

    Resolution: Fixed

> DefaultPrincipalProvider#collectGroupMembership puts wrong principal instance into the cache
> --------------------------------------------------------------------------------------------
>
>                 Key: JCR-2452
>                 URL: https://issues.apache.org/jira/browse/JCR-2452
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-core
>    Affects Versions: 2.0-beta4
>            Reporter: angela
>            Assignee: angela
>             Fix For: 2.0-beta5, 2.0.0
>
>
> DefaultPrincipalProvider#collectGroupMembership adds the passed principal instance to the cache. This may cause
> inconsistencies as the cache should only contain principals obtained from by the provider.

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


[jira] Updated: (JCR-2452) DefaultPrincipalProvider#collectGroupMembership puts wrong principal instance into the cache

Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/JCR-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jukka Zitting updated JCR-2452:
-------------------------------

    Fix Version/s:     (was: 2.1.0)
                       (was: 2.0.0)
                   2.0-beta6

> DefaultPrincipalProvider#collectGroupMembership puts wrong principal instance into the cache
> --------------------------------------------------------------------------------------------
>
>                 Key: JCR-2452
>                 URL: https://issues.apache.org/jira/browse/JCR-2452
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-core
>    Affects Versions: 2.0-beta4
>            Reporter: angela
>            Assignee: angela
>             Fix For: 2.0-beta6
>
>
> DefaultPrincipalProvider#collectGroupMembership adds the passed principal instance to the cache. This may cause
> inconsistencies as the cache should only contain principals obtained from by the provider.

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