Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 47741 invoked from network); 1 Dec 2005 13:23:14 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 1 Dec 2005 13:23:14 -0000 Received: (qmail 48679 invoked by uid 500); 1 Dec 2005 13:23:10 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 48605 invoked by uid 500); 1 Dec 2005 13:23:09 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@cocoon.apache.org List-Id: Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 48594 invoked by uid 99); 1 Dec 2005 13:23:09 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Dec 2005 05:23:09 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [212.27.42.29] (HELO smtp3-g19.free.fr) (212.27.42.29) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Dec 2005 05:24:35 -0800 Received: from [192.168.2.15] (lgp44-1-82-67-135-94.fbx.proxad.net [82.67.135.94]) by smtp3-g19.free.fr (Postfix) with ESMTP id E61AE3A957 for ; Thu, 1 Dec 2005 14:22:41 +0100 (CET) Message-ID: <438EF926.308@bluexml.org> Date: Thu, 01 Dec 2005 14:22:46 +0100 From: Jean-Christophe Kermagoret User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: fr, en MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: [Portal] Why copletdata aren't user/role profiled ? Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Hello, I discovered copletdata and copletbasedata are both global. I agree for=20 copletbasedata, but why this behaviour for copletdata ? Is it the same=20 in the 2.2 portal ? It seems to me it should be a good idea to permit a copletdata by role=20 or user to allow personalization by the user. That way, he could only=20 pick what is available in its copletdata profile and create=20 copletinstancedata based on these copletdata types. Jean-Christophe --=20 BlueXML Jean-Christophe Kermagoret Directeur associ=E9 jck@bluexml.org