[
https://issues.apache.org/jira/browse/JS2-786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12554461
]
Vitaly Baranovsky commented on JS2-786:
---------------------------------------
David, I've tested your changes to database schema. Speed up of loading
preferences is 8 times! And it is a good result!
I've made one test. One of my pages loaded 469 seconds before index
optimization, and 57 seconds after index optimization. But it is still big
time. All psml of our portal was preloaded more than 6 hours before
optimization, and about 1 hour after optimization.
And there is one big problem! Jetspeed 2.1.3 uses prefs per user. But Jetspeed
2.0 used prefs per entity. So, we can't use Jetspeed 2.1.3, because we have use
cases, when admin users configures public pages. So, we need edit-defaults
custom portlet mode.
But we have big portal, created with edit mode with Jetspeed 2.0. So, we still
need converter to convert our Jetspeed 2.0 per entity db preferences to
defaults psml preferences.
And, I think, all Jetspeed 2.0 users that use this use case has such problem
too.
So, can you create such converter? I will reopen this issue as its creator...
P.S.: Sorry I'm not answering before, I was in vacation...
> Tool for conversion preferences from database no-principal preferences to
> defaults preferences in psml pages
> ------------------------------------------------------------------------------------------------------------
>
> Key: JS2-786
> URL: https://issues.apache.org/jira/browse/JS2-786
> Project: Jetspeed 2
> Issue Type: Wish
> Components: Portlet Entities and Preferences
> Affects Versions: 2.1.3
> Reporter: Vitaly Baranovsky
> Assignee: David Sean Taylor
> Fix For: 2.1.3
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
