> What about page-specific preferences on a fragment? Have you tried
putting your preferences in the PSML?
We've developed internet portal with many sites using jetspeed 2.0. Every
site has its own non-technical admins that configure portlets using prefs.
And this modifications must to be visible for all users of portal. Admins
are not technical users, so its very hard to them to edit psml files. They
can only configure portlets using graphical interface.
Do you still want users to override these default prefs, or strictly
the "old way"? ...
Otherwise, if you want default preferences in a special
"DEFAULTS_MODE" (which I think is a good use case) ...
Its not even clear to me how this would work, or how the system would
know that its in "defaults mode"
There is "edit-defaults" custom portlet mode described in JSR-168. This
means admins can edit defaults preferences thru graphical interface of
portlet in "edit-defaults" portlet mode, and other users can overwrite this
preferences in "edit" mode (if they have appropriate permissions). I think
it is a good use case. I've posted JIRA recorded once:
http://issues.apache.org/jira/browse/JS2-634
We are running out of time on the 2.1 release
I think, developing of "edit-defaults" portlet mode is very actual
after 2.1release.
2007/2/19, David Sean Taylor <[EMAIL PROTECTED]>:
On Feb 19, 2007, at 10:29 AM, Thorsten Berger wrote:
>
>>> David,
>>>
>>> as far as I remember, I've not been able to achieve that
>>> behaviour. But that's already about two months ago, so I'd have a
>>> look at this again if the following isn't accurate (any more).
>>>
>>> The former window-specific prefs of portlet entities have been
>>> stored under a node with the name "no-principal" (e.g. /
>>> portlet_entity/welcome-1/no-principal/preferences), right?
>>> So I enabled the merging feature and set the "no-principal" prefs
>>> of the portlet entity manually in the db.
>>> The problem was, that always a preference node for the guest user
>>> (and probably for all other users too) had been created by just
>>> viewing the page. This has overridden my "no-principal" prefs.
>>>
>>> But, as in my comment to JS2-449, I'd rather completely use the
>>> old behaviour for the mentioned use case: a portal admin should
>>> be able to put portlets on a public page and configure it for all
>>> users. Is that still someway supported over the UI?
>>> I mean if the above would work and an admin user could set the
>>> "no-principal" prefs, that would probably be a solution.
>>>
>> What about page-specific preferences on a fragment? Have you tried
>> putting your preferences in the PSML?
>>
> I need a solution where ordinary administrative users can place
> portlets on pages with the customizer and set their default prefs.
> Setting fragment prefs would only be a solution for me ;)
>
>
Do you still want users to override these default prefs, or strictly
the "old way"?
If you want the old way,
what about if I changed the PortletEntityImpl.getPreferenceSet to use
a conditional configuration:
if (PREFS_PER_USER)
prefNodePath =
MutablePortletEntity.PORTLET_ENTITY_ROOT + "/" + getId() +"/"+
principal.getName() +"/"
+ PrefsPreference.PORTLET_PREFERENCES_ROOT;
else
prefNodePath =
MutablePortletEntity.PORTLET_ENTITY_ROOT + "/" + getId() +"/"+
NO_PRINCIPAL +"/"
+ PrefsPreference.PORTLET_PREFERENCES_ROOT;
Otherwise, if you want default preferences in a special
"DEFAULTS_MODE" (which I think is a good use case)
then I don't think we can get that into the customizer in this short
notice
We are running out of time on the 2.1 release
Its not even clear to me how this would work, or how the system would
know that its in "defaults mode"
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
With best regards,
Vitaly Baranovsky
