Added Indexes

Foreign Key Altering

Added Tables

Portlet API Caching

Version 2.1 is the first Jetspeed version to support Portlet API Caching. In 2.0 the expiration-cache was set to -1 (infinity time) for all layouts in the file WEB-INF\apps\jetspeed-layouts\WEB-INF\portlet.xml. When upgrading to version 2.1 or greater from 2.0, you will need to update your database to disable portlet caching on the Jetspeed layouts. Updating the layouts can be achieved by either redeploying the jetspeed-layouts portlet application, or by updating your database as shown below (assuming the APPLICATION_ID value is 2) for the jetspeed-layouts application.

UPDATE PORTLET_DEFINITION P SET EXPIRATION_CACHE = 0 WHERE P.APPLICATION_ID = 2

Portlet Preferences

Portlet Preferences are now by default user specific on all pages. In Jetspeed 2.0, for shared pages, the Portlet Preferences were shared as well.

To retain most of the old Jetspeed 2.0 behavior, allowing an administrator to still set/modify initial Preferences for other users,

modify the following setting in the registry.xml spring assembly configuration 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>        
	   

Added Tables

Column Altering

Index Altering

Foreign Key Altering