OracleAS Portal Developer Kit (PDK)
PDK New Features - PDK 9.0.4.1.0

Introduction

This release of the PDK includes new features and portlets for the building Java Portlets and PortalTools.

Java Portlets | Portal Tools

Java Portlets

Edit Defaults Mode configures Sample Portlets across all Locales

To simplify the configuration and upgrade requirements for all our sample portlets, we now use a localePersonalizationLevel of none in all the XML Provider Definition (provider.xml) files we ship in jpdk.ear. This means that the changes you make in Edit Defaults mode will apply to all users, no matter what their or your Portal session language is. If you want to use the samples with existing locale-specific data from previous releases and continue using the old Edit Defaults behaviour, simply modify the localePersonalizationLevel tag to a value of language or locale appropriately (see PDK Java 9.0.4.0.2 Release notes for for a description of these settings). If you are upgrading from a release prior to 9.0.4.0.2, you should also use the upgrade utility described below to ensure existing locale-specific data uses an appropriate naming format for your chosen localePersonalizationLevel.

Preference Store Migration / Upgrade Utility

A new command line utility has been included in pdkjava.jar that allows users upgrading from previous releases of PDK-Java and OracleAS Portal to manage portlet preference data generated by existing portlets. The tool allows upgrading users to ensure that their existing locale specific portlet preference data uses a naming format compatible with the latest PDK and Portal releases, and also allows users to migrate existing data between different preference stores (e.g. from FilePreferenceStore to DBPreferenceStore).

Portal Tools

Locale Personalization Level

The localePersonalizationLevel setting in the provider definition file (provider.xml) is now set to "none" for OmniPortlet and SimpleParameterForm portlets. In previous releases, localePersonalizationLevel was set to "language". Therefore, now when you edit the portlet defaults from Edit Defaults Mode, the changes apply to all users regardless of the language set in the current Portal session.

If you want to use these portlets with exisiting locale specific data from previous releases and use the previous Edit Defaults behavior, set the localePersonalizationLevel tag in provider.xml to the appropriate language or locale value. For a description of these settings, refer to the PDK-Java Release Notes .

Note: If you are upgrading from a release prior to 9.0.4.0.2, use the Preference Store Migration/Upgrade Utility described in the PDK-Java Release Notes to ensure that existing locale-specific data uses a naming format that matches your localePersonalizationLevel setting.

Preference Store Migration/Upgrade Utility

You can now migrate your customizations from the file preference store to the DB Preference store and vice versa. This utility is available with the JPDK version 9.0.4.1.0 and higher. More details are available in the PDK-Java Release Notes.

A complete list of new features is available within the PDK New Features article. 

Back to Top