uPortal 3 Configuration Changes

Owned by Eric Dalquist
Last updated: Feb 18, 2008Version comment
2 min read

Information on this page pertains to the uPortal 3 effort currently underway. This documentation does not apply to any version of uPortal 2 or the exploratory portal code archived in the SVN sandbox. For more information on this effort please read the uPortal 3 Development Documentation

Some configuration files have changed or been removed in uPortal 3 in relation to uPortal 2 release. These changes are linked to or documented on this page.

Removed Configuration

Configuration files and settings below have been removed in uPortal 3. The most common reason is a design change in the code or removal of deprecated APIs has made the configuration unnecessary.

UserLayoutManagerFactory & UserLayoutStoreFactory in portal.properties

The SLM & ALM examples have been removed from the configuration file. While the SLM configuration will still work the ALM configuration will not as ALM has been removed from uPortal 3.

org.jasig.portal.RDBMServices.* properties in portal.properties

RDBMServices is now a facade around DataSource objects configured in the Spring application context. As such these properties are no longer used. This also includes the 'org.jasig.portal.PooledDataSourceFactory.implementation' property.

pool properties in rdbm.properties

Now that DataSource objects are configured in the Spring application context the 'jdbcUsePool' and 'poolPreparedStatements' properties are no longer used.

org.jasig.portal.ChannelRegistryStoreFactory.implementation in portal.properties

The IChannelRegistryStore implementation is now spring configured in the properties/contexts/channelContainerContext.xml file.

org.jasig.portal.channels.portlet.CPortletAdapter.uniqueContainerName in portal.properties

The portlet container name is now generated based on the servlet context name.

org.jasig.portal.concurrency.IEntityCachingServiceFactory in portal.properties

The IEntityCachingService is now configured directly in (no IEntityCachingServiceFactory is used) as a Spring bean in cacheContext.xml
All org.jasig.portal.concurrency.IEntityCachingService.* properties are no longer used. Refer to the uPortal 3 cache configuration documentation on how to configure entity caching services in uPortal 3.

org.jasig.portal.security.PersonManagerFactory.implementation in portal.properties

The person manager is now configured as a Spring bean in the userContext.xml

Modified Configuration

org.jasig.portal.channels.CGenericXSLT.default_cache_timeout in portal.properties

Removed, if per-instance cache timeouts are needed the class will need to be extended and a specific cache instance used for the channel.

org.jasig.portal.UserInstance.* in portal.properties

These properties all pertain to the rendering pipeline code. This code is now in the org.jasig.portal.rendering.StaticRenderingPipeline class.