[JS2-786] Tool for conversion preferences from database no-principal preferences to defaults preferences in psml pages

• Type: Wish
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.2.0
• Fix Version/s: 2.2.0
• Component/s: Portlet Entities and Preferences
• Assignee: David Sean Taylor
• Reporter: Vitaly Baranovsky
• Created: 08/Oct/07 16:22
• Updated: 04/Oct/11 21:08
• Resolved: 04/Jun/08 17:12

Description

With jetspeed 2.0 version all preferences was per entity. But all preferences become per user with release of jetspeed 2.1.
But people with Jetspeed 2.0 have important use case: admin configures portlets on public portal pages for all users (include guests).
So, people with Jetspeed 2.0 can't migrate to 2.1 version (and later versions).

edit-defaults custom portlet mode (https://issues.apache.org/jira/browse/JS2-634) can solve this problem. But people with Jetspeed 2.0 can't use edit-defaults portlet mode, because edit-defaults custom portlet mode stores preferences directly in psml pages, and there is no conversion tool to convert no-principal preferences from database to psml pages.

So, there is need for conversion tool that moves no-principal preferences from db directly to psml pages.

This is the only way to migrate to Jetspeed 2.1.3 for company that uses important use case described above.