Return-Path: Delivered-To: apmail-portals-jetspeed-user-archive@www.apache.org Received: (qmail 76417 invoked from network); 23 Jan 2006 21:30:07 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 23 Jan 2006 21:30:07 -0000 Received: (qmail 1039 invoked by uid 500); 23 Jan 2006 21:30:03 -0000 Delivered-To: apmail-portals-jetspeed-user-archive@portals.apache.org Received: (qmail 991 invoked by uid 500); 23 Jan 2006 21:30:03 -0000 Mailing-List: contact jetspeed-user-help@portals.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Jetspeed Users List" Delivered-To: mailing list jetspeed-user@portals.apache.org Received: (qmail 972 invoked by uid 99); 23 Jan 2006 21:30:03 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Jan 2006 13:30:03 -0800 X-ASF-Spam-Status: No, hits=1.4 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: 217.113.224.27 is neither permitted nor denied by domain of jacek.wislicki@gmail.com) Received: from [217.113.224.27] (HELO mailout.toya.net.pl) (217.113.224.27) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Jan 2006 13:30:02 -0800 Received: from localhost (unknown [192.168.120.26]) by lazir.toya.net.pl (TOYAnet MailServer) with ESMTP id 7E4898BCFD for ; Mon, 23 Jan 2006 22:29:38 +0100 (CET) Received: from lazir.toya.net.pl ([192.168.120.25]) by localhost (agregat [192.168.120.26]) (amavisd-new, port 10024) with ESMTP id 31106-02 for ; Mon, 23 Jan 2006 22:29:26 +0100 (CET) Received: from [10.1.202.6] (unknown [10.1.202.6]) by lazir.toya.net.pl (TOYAnet MailServer) with ESMTP id 8415B8BD0E for ; Mon, 23 Jan 2006 22:29:26 +0100 (CET) Message-ID: <43D54AC9.9020505@gmail.com> Date: Mon, 23 Jan 2006 22:29:45 +0100 From: =?ISO-8859-2?Q?Jacek_Wi=B6licki?= User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Jetspeed Users List Subject: Re: Retrieving a portlet's unique instance ID.. References: <48309.127.0.0.1.1137893193.squirrel@jeanne.rwhmax.org> <43D2ECC2.4060403@gmail.com> <57358.127.0.0.1.1137903553.squirrel@jeanne.rwhmax.org> <43D32B2E.20309@gmail.com> <43D498E3.3020705@bluesunrise.com> <58980.127.0.0.1.1138050155.squirrel@jeanne.rwhmax.org> In-Reply-To: <58980.127.0.0.1.1138050155.squirrel@jeanne.rwhmax.org> Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit X-TOYA-AV: AntyVir-Skaner at toya.net.pl X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Wiadomosc od jetspeed@theunderground.net z 2006-01-23 22:02 brzmiala: > Anyone out there have thoughts on this? Am I thinking about this > incorrectly, or is this a time when a portlet has a legitimate reason for > fetching a unique identifier? And using fragment IDs works fine in this situation. The case of manual setting preferences has another drawback - the default j2-admin application displays only a list of fragment identifiers and it is very difficult (impossible?) to identify the fragment one needs, especially in case where the IDs are automatically generated by Jetspeed (like 'P-108c087e90f-10001'). -- pozdrawiam, Jacek Wislicki jacek.wislicki@gmail.com tel.: +48 502 408 444 gg: 2540358 skype: jacek_wislicki --------------------------------------------------------------------- To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org For additional commands, e-mail: jetspeed-user-help@portals.apache.org