My original question was a bit vague. We have several different portlet applications (PA). Each PA has a set of folders/pages it defines. We are using the folder-based pages and not the database. We have a common way for users to configure each PA’s pages at the click of a button using the Jetspeed APIs. Users can’t edit these pages but they can change each portlet’s preferences on these pages. When a PA comes out with a new release it’s likely the set of pages for the PA needs to be updated (new pages, portlets added/removed from existing pages, pages removed). Ideally, we’d be able to do something like delete the existing user’s page for the PA and copy the new PA’s template pages. However, we don’t want to lose the user’s preferences for any portlets that previously existed on pages that were just updated. It’s not an issue for new pages or deleted pages. We want to do this without the user having to do anything possibly at login time, or at server startup time, or even through some process we develop that runs when the server is down (like part of our installer). Any ideas are much appreciated. We don’t want to orphan any preference settings in the database either.
Thanks again, in advance, -- View this message in context: http://old.nabble.com/Existing-PSML-page-updates-tp29335997p29349197.html Sent from the Jetspeed - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
