AquaLogic .NET Application Accelerator 1.1 MP1 - released June 2008

AquaLogic .NET Application Accelerator 1.1 - released March 2008

The AquaLogic .NET Application Accelerator 1.1 packages components required to develop ASP.NET portlets. The product packages existing functionality for ALI portlet development and adds new components and features for WSRP portlet development.

AquaLogic .NET Application Accelerator 1.1 includes the following:

• Web Control Consumer 3.1: Supports authoring portlets using ASP.NET 2.0. This component is the same version as included in .NET Application Accelerator 1.0.
• AquaLogic .NET Portlet API 1.1: Provides ease-of-use APIs for the IDK and WSRP portlets.
• AquaLogic .NET WSRP Producer 1.1: Provides a standards-compliant WSRP 1.0 Producer for ASP.NET 2.0 web sites.

The AquaLogic Interaction Development Kit (IDK) 6.0 is installed with AquaLogic .NET Portlet API 1.1.

Note: ASP.NET 1.1 is unsupported. The Web Control Consumer does not support SSL or Web Parts. SharePoint Web Parts are unsupported.

These release notes cover the AquaLogic .NET Application Accelerator 1.1.

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.

The BEA licensing framework has been removed from this product entirely. There is no need to obtain or use a license key to enable any functionality in this version.

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

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.

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

The product distribution includes the following documents in the Documentation folder.

The AquaLogic .NET Application Accelerator 1.1 provides the following new features:

• AquaLogic .NET Portlet API 1.1
  • Updated Microsoft Visual Studio 2005 web site project template for WSRP portlets
  • Microsoft Visual Studio 2005 web application project template for WSRP portlets
  • Updated Microsoft Visual Studio 2005 file templates for WSRP portlet pages
  • Improved WSRP portlet API that no longer requires a special base page and provides simplified access to WSRP portlet properties, registration information, portlet mode, and window state
  • WebLogic Portal (WLP) SAML token and UNT authentication to WSRP portlets
• AL .NET WSRP Producer 1.1
  • Support for WSRP registration and portlet management interfaces
  • Support for all standard as well as custom portlet modes and window states
  • Support for localization of portlet markup and portlet metadata
  • SSL support
  • Enhanced support for inter-page navigation using Response.Redirect or Server.Transfer

• WSRP portlets do not maintain view state between two WebLogic Portal pages. (Issue #54573)
• WSRP Producer's wsrp-producer.xml does not allow multiple instances of the description element for a single portlet. (Issue #54913)
• WSRP Producer returns invalid portlet mode "Bea.Types.Portlet.PortletMode[]" to Consumer. (Issue #55131)
• WSRP portlets don't support the minimize/maximize window states. (Issue #55139)
• WSRP Producer's portlets.xml is not automatically reloaded after it is changed on the file system. (Issue #55284)
• WSRP Producer does not support edit/help view modes. (Issue #55302)

• Uninstaller deletes the wsrp-producer.xml file when removing the WSRP Producer. (Issue #54495)
• ReportViewer control does not work with WSRP. (Issue #54352)
• js includes and image downloads fail when using UNT to IIS authentication. (Issue #65049, #65054, #66566 and #66579)
  
  Workaround: The method used to require authentication for a ASP.NET portlet but not for portlet resources depends on the type of authentication required by the portlet application:
  1. If you are using ASP.NET Forms authentication or the SAML authentication, configure the mime-type mappings in IIS for your application so that requests for javascript, image, and other external resource content types are not processed by ASP.NET. This is the default in IIS so generally requires no modifications.
  2. If you are using Windows (IIS) authentication, move all external images, javascript files and css style sheets to a virtual directory or separate server that is configured to not require authentication in IIS. Take note that many ASP.NET controls and components use the WebResources feature to dynamically emit external javascript and image references in your markup. To make sure that WebResources references do not require authentication, ensure that any virtual paths from which WebResources.axd references originate do not require authentication. In general, this is simply the root of your ASP.NET portlet application.
• .NET WSRP Producer may return markup that contains disallowed elements, e.g. <html>, <body>, <frame>, <frameset>, <head> or <title>. (Issue #66592)
• WebLogic Portal only accepts users with credential mapping on an instance configured to send User Name Tokens ("Unable to add security token for identity" exception will be thrown). (Issue #67230)
  
  Workaround: All portal users must have credential mapping on a WebLogic Portal instance configured to send User Name Tokens.
• .NET Portlet Toolkit creates a redundant add/remove program entry: BEA .NET Portlet API Help. (Issue #66916)