Mailing-List: contact jetspeed-user-help@portals.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jetspeed Users List" <jetspeed-user@portals.apache.org>
Received-SPF: neutral (asf.osuosl.org: 217.113.224.27 is neither permitted nor
 denied by domain of jacek.wislicki@gmail.com)
Message-ID: <43D6F672.2090107@gmail.com>
Date: Wed, 25 Jan 2006 04:54:26 +0100
From: =?ISO-8859-2?Q?Jacek_Wi=B6licki?= <jacek.wislicki@gmail.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: Jetspeed Users List <jetspeed-user@portals.apache.org>
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>
 <43D4CCDE.5010502@gmail.com> <43D6E5CC.5010506@bluesunrise.com>
In-Reply-To: <43D6E5CC.5010506@bluesunrise.com>
Content-Type: text/plain; charset=ISO-8859-2; format=flowed
Content-Transfer-Encoding: 7bit

Wiadomosc od David Sean Taylor z 2006-01-25 03:43 brzmiala:

>>> A portlet isn't really supposed to know about its 'unique id' as that 
>>> is an implementation detail of the portal.
>> However, when I managed to get the current fragment ID, I was able to 
>> create a universal portlet class whose behaviour, displayed contents 
>> and some security features are determined by some data stored in the 
>> database (fragment preferences were not enough for storing large 
>> amounts of data).
> What if you stored a unique key in the preference, say "content-id"
> This unique is portlet instance specific.
>  From there, you can map to your large amounts of data
But adding a preference is a manual process AFAIK and would require 
switching between different J2 admin applications when adding new 
fragments, not to mention possible human mistakes in typing the 
preference name, value and holding its uniqueness. Unless some 
modifications are done to portal mechanisms and the process becomes 
human-independent.

Furthermore, here the preference value would be just another unique ID 
(could have just the same value as the fragment ID). Is there a reason 
why you don't like such a solution other than portal and portlet logic 
assumptions?

>>> If you want to write portlets specific to Jetspeed-2, have a look at 
>>> the j2-admin app which accesses portal services in the 
>>> jetspeed-portlet.xml
>> By the way, is the bug concerning service access fixed?
> You mean this one:
> https://issues.apache.org/jira/browse/JS2-464
> I'll try to get a look at it tonight
Thanks :)

-- 
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