Overview
uPortal 3.0 has been refactored to provide for a clear long term uPortal development roadmap. This refactoring includes using Maven 2 for build management, a unified Spring based configuration, data import and export utilities for all data types, and use of Pluto 1.1 for portlet rendering.
Requirements
uPortal 3.0 requires JDK 1.5 or later and will compile and run under JDK6.
Release Notes
Hangups – Changes in 3.0 that might trip you up
Fixes in 3.0.1
- ProxyServlet security vulnerability
- Various import/export script fixes including; export user-prefs from Oracle, import entity-types with certain group services.
- Restored CacheLdapSecurityContext (was missing in 3.0.0)
- Local LDAP authentication now works
- https URLs now work for portlets
- Resolved issue with password manager channel failing for non-local users
- Resolved UI issues when adding a channel that fails to render
- Removed .zip packaging of uPortal distributions due to issues in the Windows Extractor tool
Enhancements in 3.0.1
- JSR-168 specification CSS classes
- dbloader fails-fast if no mapping is found in dbloader.xml
- Allow uP_fname & uP_args for guests
- Allow more options for portlet preference loading for guests
- VersionManager now populates "Powered By" string in theme
- Added mediating factory bean to try multiple lazy-init beans by name and use the first one that instantiates without exception
- Created a hidden category for channels to allow easier management
- Updated patch revisions of all portal dependencies
Enhancements in 3.0.0 not present in any 2.6.x release
- Maven 2 build management system which provides dependency management, build, test, and packaging functionality. An integrated Ant build script is also included to support all of the necessary Ant tasks from previous uPortal versions.
- A single, consolidated Spring application context has been created and all new development for the framework is being done in a managed Inversion of Control fashion. This includes refactoring of some uPortal service classes and factories to provide the implementations via the Spring application context.
- Deprecated code removal. Much of the code marked as deprecated in uPortal 2.6 has been removed and legacy static factory classes are being marked as deprecated where appropriate.
- Aggregated Layout Manager (ALM) has been removed from the uPortal 3.0 code base. The ALM code has been moved into the contrib directory in version control to allow interested parties to continue development against the code.
- Switch to the stand alone Person Directory library. The Person Directory code has been removed from uPortal and replaced with the API compatible stand-alone version of the code.
- Upgraded to Pluto 1.1. This change involved removing and re-writing all JSR-168 portlet support code. This change provides more complete portlet support and aligns uPortal with the Pluto JSR-286 work.
- Refactored rendering pipeline and channel rendering management code removing many instance scoped variables in favor of request attributes.
- Moved all URL processing code into a dedicated request parameter processing pipeline which executes before the rendering pipeline starts.
- A new XHTML/CSS based theme and skin that has a straight-forward directory and file structure.
- Revised default content that better demonstrates the features and functionality of uPortal.
Enhancements in 3.0.0 that may also appear in a 2.6.x release
- Data import and export tools. Andrew Wills has provided Cernunnos based scripts to import and export all uPortal data. These scripts provide a data migration patch when upgrading between versions of uPortal including uPortal 2.5 or 2.6 to 3.0
