Release Notes for AquaLogic Interaction JSR-168 Container 1.2
Contents
Version History
Release Notes Overview
Version 1.2
Supported Operating Systems, Application Servers, and Browsers
Supported BEA Products
Documentation
New Features
Issues Addressed
Known Issues
Version 1.1
New Features
Issues Addressed
Known Issues
Version History

AquaLogic Interaction JSR-168 Container 1.2 released April 2007 for Windows and Solaris, AIX, Linux, and HP-UX

AquaLogic Interaction JSR-168 Consumer 1.1 released October 2006 for Windows and Solaris

Release Notes Overview

These release notes cover all releases of AquaLogic Interaction JSR-168 Container 1.2, including patches and maintenance packs. For information on a particular release, please go to the appropriate section of these release notes.

Release notes are occasionally updated after the release date. For the most up-to-date release notes, go to http://www.oracle.com/technology/documentation/index.html.

Version 1.2
Supported Operating Systems, Application Servers, Databases, and Browser

Refer to the Interoperability page in the Product Center at support.plumtree.com for the latest information on supported operating systems, application servers, databases, and browsers.

At the time of release, AquaLogic Interaction JSR-168 Container 1.2 supports the following:

- Operating Systems: AIX 5.3 (on POWER3, POWER4, POWER5); HP-UX 11i V2 (on Itanium); RedHat Enterprise Linux 4 update 3 (on x86); Solaris 8, 9, and 10 (on SPARC); SUSE Enterprise Server 9 (on x86); Windows Server 2003 SP1 or R2 (on x86)

Supported BEA Products

Refer to the Interoperability page in the Product Center at support.plumtree.com for the latest information on supported BEA products.

At the time of release, AquaLogic Interaction JSR-168 Container 1.2 supports the following:

- AquaLogic Interaction 6.1 MP1, 6.1.0.1, and 6.1
- Plumtree Foundation 6.0 SP1, and 6.0
- Plumtree Corporate Portal 5.0.5, and 5.0.5J

Documentation

The following product documentation is available for download from http://www.oracle.com/technology/documentation/index.html:

Document | Document Description
--- | ---
AquaLogic Interaction JSR-168 Container Installation and Upgrade Guide | Describes how to install and upgrade the components of AquaLogic Interaction JSR-168 Container 1.2.
Administrator Guide for the AquaLogic Interaction JSR-168 Container | Describes how to develop portlets using the AquaLogic Interaction JSR-168 Container 1.2.

The following product documentation is distributed with the release package:

Document Title and File Name | Document Description
--- | ---
Attributions JSR-168Container_Attributions.txt | Provides a list of third-party technologies used in the product, along with licensing information.

Version 1.2
New Features

- AquaLogic Interaction JSR-168 Consumer has been renamed AquaLogic Interaction JSR-168 Container.
- Additional logging information can now be gathered through the AquaLogic Interaction Logging Utilities.
- AquaLogic Interaction JSR-168 Container 1.2 now installs into ptjsr168/1.2.
- The AquaLogic Interaction JSR-168 Container 1.2 starter application has been updated to use the 5.4 version of the IDK.
- AquaLogic Interaction JSR-168 Container now supports Java 1.4 and Java 5.0.
- Samples have been included that show the use of the IDK.
- The display name of the devkit Web Application template has been renamed from "PtPortletContainer" to "ALI JSR-168 Portlet Template".

Issues Addressed

- The JSR-168 Container has now been tested using non-English locales. (Issue #37787)
- The JSR-168 Container can now support mime-type */* or atype/* as per the JSR-168 standards (Issue# 46152)
- Individual requests are now logged through log4j. (Issue# 55718)
- After performing several actions on any of the sample portlets, the browser will no longer return to the Portal Home Page. (Issue# 58016)
- The portlet.xml file is now parsed according to JSR 168 specifications, and mode switching via the ActionResponse.setPortletMode(...) method is now supported. (Issue# 52598)
- The portlet:actionURL tag now directs to the appropriate mode and retains the mode for subsequent render requests. The portlet:renderURL tag now respects the mode indicated in the JSP tag. (Issue# 52614)
- In order to help facilitate IBM WebSphere hot deploy, the ContextListener class modifier has been changed to public. (Issue# 55980)
- When using JSR-168 Container with any version of AquaLogic Interaction 6.0 and above: portlets on a page now share a session. The workaround of using Portlet Context is now no longer required. (Issue# 32117)

Known Issues

- When running the JSR-168 container on WebSphere, the method PortletContext.getRequestDispatcher does not return null when an invalid path is passed in as an argument, because the underlying call to the WebSphere JVM ServletContext.getRequestDispatcher does not return null for an invalid path. This method works correctly on other JVMs. (Issue# 49037)
- The Help and Edit modes for <portlet:actionURL> do not refresh within the context of a portlet. The work-around is to use JavaScript to redraw the Help and Edit screens within the portlet, or to open a pop-up window. (Issue# 58100)
- AquaLogic Interaction does not support portal-defined custom window states or custom portlet modes. View, edit, config, and help are the only supported modes. (Issue# 58113)

Version 1.1
New Features

- Plumtree JSR-168 Consumer has been renamed to AquaLogic Interaction JSR 168 Consumer 1.1

Issues Addressed

- Render parameters are not stored between requests. This specifically fails the Sun TCK tests using WebLogic on Unix. (Issue #37783)
- When using Plumtree Corporate Portal 5.0.5 or below: portlets on a page do not share sessions. The portlet specification assumes that portlets on the same page share the same session, whereas portlets on the Plumtree portal always have their own session. (Issue #32217 and #34701)
- The scope of exported variables for renderURL and actionURL tags has been incorrectly set to javax.portlet.PortletURL instead of String. (Issue #37785).

Known Issues

- Including html pages in a PortletRequestDispacher fails on WebLogic Server. This is because the JSR-168 specification requires us to return null, even though WebLogic Server is expecting a result. (Issue #37784)
- The Portal and JSR-168 portlet cannot be on the same application server if the portlet uses a period (.) as the gateway space. (Issue #37786)
  Workaround: Use the servlet context (web app name) as the gateway space for the portlet.