Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Message-ID: <4391166C.7000503@apache.org>
Date: Sat, 03 Dec 2005 04:52:12 +0100
From: Carsten Ziegeler <cziegeler@apache.org>
User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: [Portal] Why copletdata aren't user/role profiled ?
References: <438EF926.308@bluexml.org> <438F0E20.5010305@dslextreme.com>
 <438F6D17.9040405@babelobjects.com> <438F729E.6060402@dslextreme.com>
In-Reply-To: <438F729E.6060402@dslextreme.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Ralph Goers wrote:
> I went and glanced at GroupBasedProfileManager.  That is a new class 
> Carsten wrote for 2.1.8 and it behaves a little differently then the old 
> profile manager. However, it is still using the pipeline to load the 
> CopletData and CopletBaseData. It checks the validity and if it is 
> cached it will use the cached version.  So if your pipeline causes 
> different cache keys to be used for different roles than this should 
> work, as far as I can tell. (See method getGlobalDatas()).
> 
Yepp :)

Now, actually I think it makes sense that coplet data and base data are
global. But it'S true that a support for roles/groups etc. is missing a
little bit. I don'T have access to the code right now and I fear I'll be
offline for the next two weeks again, but I think that you can add role
information to a coplet data. By this you define for which roles the
coplet data should be available. Now, when you create instances for a
user you simply check if the user has the role defined in the coplet data.

HTH
Carsten

-- 
Carsten Ziegeler - Open Source Group, S&N AG
http://www.s-und-n.de
http://www.osoco.org/weblogs/rael/