Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Date: Wed, 23 Nov 2011 13:01:40 +0000 (UTC)
From: =?utf-8?Q?Michael_D=C3=BCrig_=28Assigned=29_=28JIRA=29?=
 <jira@apache.org>
To: dev@jackrabbit.apache.org
Message-ID: 
 <1945263402.5817.1322053300251.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <828909354.5677.1322047899994.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Assigned] (JCR-3156) Group#getMembers may list inherited
 members multiple times
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


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

Michael D=C3=BCrig reassigned JCR-3156:
----------------------------------

    Assignee: Michael D=C3=BCrig
   =20
> Group#getMembers may list inherited members multiple times
> ----------------------------------------------------------
>
>                 Key: JCR-3156
>                 URL: https://issues.apache.org/jira/browse/JCR-3156
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-core, security
>    Affects Versions: 2.2, 2.3
>            Reporter: angela
>            Assignee: Michael D=C3=BCrig
>             Fix For: 2.4
>
>         Attachments: JCR-3156.patch
>
>
> i just happen to detect the following regression that seems to be introdu=
ces quite a while ago:
> Group#getMembers is defined to return all group members including those i=
nherited by another group being member of that group.
> Example:
> User t
> Group a : t is declared member
> Group b : t is declared member
> Group c : a, b are declared members
> The expected result of Group.getMembers was: a, b and t.
> What is currently happening is that t is included twice in the returned i=
terator.
> Quickly testing on jackrabbit 2.0 revealed that this used to work before.=
..
> I didn't carefully check when that bug has been introduced but the the re=
factoring of the membership
> collections seems to be a possible culprit.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs: https://issues.apache.org/jira/secure/ContactAdministrators!default.jsp=
a
For more information on JIRA, see: http://www.atlassian.com/software/jira