Re: [uportal-dev] Identifying portlets

Eric Dalquist Fri, 14 Dec 2007 10:40:05 -0800

No, the portlet spec doesn't provide any sort of publish/subscribe identification to the portlet, that was the purpose of the PortletPreferences APIs. May I ask why you are moving away from prefs? If the need is more flexible storage one option would be to generate a synthetic key and store that in the preferences.


Such as:
portlet checks for pref named "DataKey"
if it exists the value is used as the initial database key.

if it does not exist a new database key is created and stored in the preferences for future use.


-Eric

Jen Bourey wrote:

I was actually looking to migrate from using portlet preferences to just using database tables. I'd like to link the information to the individual portlets so that the configurations can stay per-portlet rather than per-user. Is there any kind of unique ID available for each portlet configuration?
- Jen
On Dec 14, 2007 11:59 AM, Eric Dalquist <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote:
    Portlet preferences, they are scoped by user & subscribe ID.

    -Eric

    Jen Bourey wrote:
    > Hi all,
    >
    > Is there a way to get the subscribe id for a particular portlet
    > instance?  I'd like to be able to save data per portlet
    subscription.
    >
    > - Jen
    > --
    > You are currently subscribed to [email protected]
    <mailto:[email protected]> as:
    [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
    > To unsubscribe, change settings or access archives, see
    http://www.ja-sig.org/wiki/display/JSG/uportal-dev


--
You are currently subscribed to [email protected] as: [EMAIL 
PROTECTED]
To unsubscribe, change settings or access archives, see 
http://www.ja-sig.org/wiki/display/JSG/uportal-dev

smime.p7s
Description: S/MIME Cryptographic Signature

Re: [uportal-dev] Identifying portlets

Reply via email to