On Feb 16, 2007, at 5:17 AM, Vitaly Baranovsky wrote:
There is a problem with the compatibility between version 2.1 and
version
2.0.
"Edit" mode in version 2.0 works like "edit_defaults" custom
portlet mode.
So, people with Jetspeed 2.0 have important use case: the admin
configures
portlets on public portal pages for all users (include guests). But
Jetspeed
2.1 has user specific preferences.
So, when company changes its site from Jetspeed 2.0 to Jetspeed
2.1, all
portlets will be with empty preferences (for all users and guests).
So, what can company do with site written with Jetspeed 2.0 to
succesfully
migrate to Jetspeed 2.1?
There is a setting in the registry.xml spring assembly for the
portletEntityAccessImpl component:
<!--
All preferences were shared. With JS2-449, preferences
are now
stored 'per user'. The username is stored in the
preferences FULL_PATH
To turn on mergeSharedPreferences configure this
property to true
This will NOT turn off per user prefs,
but instead merge with them, where user prefs override.
boolean
-->
<constructor-arg type="boolean">
<value>false</value>
</constructor-arg>
This should provide a migration path for preferences to move to the
new implementation
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
