IBM WebSphere Portlet Factory Version 6.0.1.1
This edition applies to version 6.0.1.1 of IBM WebSphere Portlet Factory and to all subsequent releases and modifications until otherwise indicated in new editions.
(C) Copyright International Business Machines Corporation 2007. All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
This document contains information about updates to WebSphere Portlet Factory provided by the fixpack for Version 6.0.1. This fixpack is the first to include the fixes and updates for Portlet Factory Version 6.0.1. For details about previous updates and fixes, refer to information provided at the download page for each fixpack. The download pages are available from the support site at the following URL:
http://www.ibm.com/support/search.wss?rs=3044&tc=SSRUWN%2BSS3LP9&q=fixpack
The following defects are addressed by this fixpack.
If an XML formatted result was returned in an operation, the attributes were being lost. This problem is fixed to include the attributes in the result.
In some applications built with WebSphere Portlet Factory, session objects used by WebSphere Portlet Factory were holding references to objects that are only needed during processing of a single request. With this fix, these objects are now released at the end of each request. This change decreases the overall session memory consumption of WebSphere Portlet Factory applications.
WebSphere Native web.xml has moved to project for use with UTE. You can no longer have both an application UTE and portal UTE, because the web.xml needed by each of those is different. For UTE configurations, the appropriate template is moved to the WEB-INF\ directory.
This problem occurred when submitting a form using Ajax with either the Ajax Region builder or with the Post Action Behavior options of the page action builders. If you did such a form submission and the character encoding was not UTF-8, the incoming form data would be incorrectly decoded, resulting in corrupt characters.
This bug is a combination of Rational Application Developer UTE default settings and how Portlet Factory works. Portlet Factory now limits portlet.xml updates to model save actions. Do not use auto publish in a UTE server configuration. Also, set classloading to PARENT_LAST in your ear.
Two new methods facilitate retrieving a path or an id of an item in the Content Model: getIdForPath(String path) and getPathForId(String id)
Remote schemas are no longer loaded when web.xml is being loaded into JDom.
The Form Submit action used with a non-default Post Action Behavior (for example, "Refresh specified page location after running action") generated code which would execute the specified action without actually submitting the form. This would lead to an empty RequestInputs object and null ${Inputs} references.
In the Cooperative Portlet Source Builder, if the Type selected is either Property Broker Link or Property Broker Action, the Output Name Type is no longer required. Leave this input blank. If no Output Name Type is specified, the output type uses the xsd primitive that was specified in the Output Type input (for example, xsd:string).
In the Cooperative Portlet Target Builder, the Input Type Name and the Output Name Type are no longer required. Leave these inputs blank. If no Input Type Name or Output Name Type is specified, the type uses the xsd primitive that was specified in the Input Type or Output Type input (for example, xsd:string).
In addition to the existing xsd primitive types, the following new ones have been added: xsd:byte, xsd:int, xsd:double, and xsd:dateTime.
If you create a model with multiple web services and subsequently make another model to consume these services, for every operation, you get a schema that is labeled in a sequence (schema1, schema2, schema3). The names provide no information about which schema to use for which operation.
A schema is a collection defined elements and types that is idenified by its namespace. Because there is no way to give to a schema a unique name that is meaningful, the fix to this problem associates the schema name and the namespace. In the Choose Variable Type widget, a new text area shows the namespace when the user selects a variable type.
This problem could happen when Category View was used to display data with certain types of complex structures, including multiple levels of hierarchy. In these cases, rows could be incorrectly omitted from the display.
This problem occurs during project creation if you add a featureset that has a JAR in WEB-INF\lib, and then refresh featuresets by means of the project property page. The methods for administering classpaths on the project are different between all Portlet Factory versions. There is now a test for the existence of these libs in the classpath, and do not add them again.
The webengine and j2eedeployment handler servlets were added to the portal UTE web.xml template to allow for running in the following modes:
This problem is intermittent on Windows XP and chronic on Windows 2000. There was an ant bug in the replace task when operating on large files. A custom ant task now sets the application context in web.xml.
Added exception handling in the task now ensures that the password is not null.
The J2eeDeployment handler is now configured in web.xml if you use WebSphere Portal UTE.
The J2eeDeployment handler is now configured in web.xml if you use WebSphere Portal UTE.
The existing createDocument Data Service requires two IXml inputs, one for the create criteria and the other for the document detail. Because the Service Operation builder currently only allows for one IXml input structure, it is difficult to use createDocument in a service provider model.
A new Data Service called createDocumentWithCriteria requires only a single IXml structure that contains both the create criteria and document detail. This new data service can be easily exposed by a Service Operation builder.
A necessary adjustment to the classpath on the decoder task fixes this problem.
A NullPointerException could be thrown at execution time when the following conditions were true: the Domino Data Access builder was used in a service provider model, the advanced "Fetch Subsets of Data" input was checked, the "Row Count Calculation" input was set to "leave count unspecified", and a page beyond the first page of data was navigated to from the consumer model.
In WebSphere Portlet Factory Version 6.0.1, the prefix "call" and suffix "execute" were removed from the generated operation names. This change caused a backward compatibility problem for existing services with operations defined using the previous naming convention. To resolve the problem, a property "bowstreet.definition.expand.opname" is added to allow you to continue generating WSDL with the previous naming convention for backward compatibility for existing clients. The property value "bowstreet.definition.expand.opname=false" defaults to false. If you set the property to true, the old naming convention with the prefix "call" and suffix "execute" is used for the operation names.
When the Credential Builder was used in JSR-168 portlets and the credential slot did not exist for the specified resource, you would receive an exception when this builder tried to create a new slot.
The fix also addresses an issue where you get an exception in some cases if you ask for credentials that have not been set. Now a null value is returned instead of the exception.
This change addresses two problems when multiple outputs are specified in the Cooperative Portlet Source Builder.
The generated property broker WSDL is missing references to the additional outputs. The order of the parameters passed to the generated property broker action method could be transposed.
Improvements in memory usage were made to the Excel Import builder. As a best practice, use a Cache Control builder to cache the results of the LJO method, getContentXML().
This problem existed when exposing an operation as a web service that uses an imported xsd file. If the xsd file (defined in a schema builder) uses a relative path, the generated wsdl prefixes the relative path with a hard-coded absolute path (the file path on the server). A client of the service cannot load this included schema file from a file path. The fix finds the relative path of the file to the project and prefixes the path with an HTTP URL.
LO19372 -- Resolves fix Ref 29374 above.
LO20193 -- Resolves fix Ref 29504 above.
LO20505 -- Resolves fix Ref 29305 above.
Refer to WebSphere Portlet Factory 6.0.1 Release Notes.
Refer to WebSphere Portlet Factory 6.0.1 Release Notes.
In addition, note that Portlet Factory now supports all versions of the zOS operating system that are supported by WebSphere Portal 5.1.
To apply this fixpack to an installed copy of WebSphere Portlet Factory 6.0.1:
Exit WebSphere Portlet Factory 6.0.1 Designer. Then, note the path where Portlet Factory is installed. Supply this information during the fixpack installation.
Extract the contents of the fixpack to a convenient location on the machine where Portlet Factory Designer is installed.
Locate and run the Fixpack.exe file.
Follow the instructions in the fixpack installation program to apply the fixpack to the installed version of WebSphere Portlet Factory 6.0.1.
To verify that the fixpack was correctly installed:
Start Portlet Factory Designer.
In the Eclipse Help menu, select About Eclipse SDK.
In the About Eclipse SDK window, click the IBM WebSphere Portlet Factory icon.
In the About Eclipse SDK Features screen, note that the Portlet Factory Designer version is 6.0.1.1.
After you apply this fixpack to Portlet Factory Designer, modify previously created projects to incorporate fixpack improvements. To incorporate fixpack changes into a project, follow these steps:
Start Portlet Factory Designer and load a project.
In the navigator, right-click project and click WebSphere Portlet Factory Project > Upgrade Project Version.
When prompted, click OK. The project is upgraded to use the latest plug-in components.
Click Yes to deploy the project and upgrade the deployed development and portlet WAR files.
To remove this fixpack from an installed copy of WebSphere Portlet Factory 6.0.1:
Close Portlet Factory Designer.
Open the Windows Control Panel and select Add or Remove Programs.
In the Installed Programs list, select the WebSphere Portlet Factory Fixpack 6.0.1.1 program.
Click Change/Remove to start the fixpack uninstall program.
Click Next to uninstall the fixpack.
Follow these steps to remove fixpack enhancements and changes to the software. Note that you will have to modify your projects by hand if you have made any changes to them between installing and uninstalling the fixpack as you would between any version change.
Remove the fixpack from Portlet Factory Designer. (See Section 3.0 above.)
Start Portlet Factory Designer and load the project.
In the project's right-click menu, select: WebSphere Portlet Factory Project > Modify.
When prompted, select OK to initiate the process of restoring 6.0.1 product files. Project Factory displays a confirmation box. Click OK to continue.
The New Project Wizard Add Feature Sets page is displayed. Note that Feature Sets previously installed in the project are selected. These Feature Sets must now be reinstalled to override fixpack changes.
Click Next to restore the selected Feature Sets.
As Additional Project Wizard screens are displayed, click Next to accept 6.0.1 project settings.
Click Finish to complete project rollback.
Portlet Factory modifies the project files. When the first file that the process would overwrite is encountered, Portlet Factory prompts you to overwrite the file (Yes), retain the file in its current form (No), overwrite all existing files (Yes to All), or leave all existing files in their current state (No to All).
Restart the WebSphere Application Server to insure project changes are picked up in the deployed project WAR file.
As of May 15th 2006, all support for Bowstreet and new IBM derivative products is being provided through IBM Customer Support. All Bowstreet email and electronic incident submission systems have been replaced by the IBM Electronic Service Request (ESR) system.
In addition, new support forums have been created on IBM developerWorks. Included are 8 different forums for the IBM Portlet Factory and 4 forums for the IBM Workplace Dashboard. These forums are available to external customers and they will be monitored by IBM resources. Links to these forums are included in the support announcement.
Call 800-IBM-SERV (800-426-7378) in the US and Canada. When calling from outside the US or Canada, please call the appropriate number below:
Europe, Middle East and Africa: +44(0)1475-897169
Inside Australia: 131-426 or 1-800-257373
You can directly submit support tickets to IBM. For more information on the IBM ESR sytem, refer to the following URL:
http://www.ibm.com/software/support/probsub.html
This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject
matter described in this document. The furnishing of this document does
not grant you any license to these patents. You can send license inquiries,
in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive Armonk, NY 10504-1785 U.S.A.
For license inquiries regarding double-byte (DBCS) information, contact
the IBM Intellectual Property Department in your country or send inquiries,
in writing, to:
IBM World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106-0032, Japan
The following paragraph does not apply to the United Kingdom or any
other country where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS
IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING,
BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY
OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer
of express or implied warranties in certain transactions, therefore, this
statement may not apply to you.
This information could include technical inaccuracies or typographical
errors. Changes are periodically made to the information herein; these
changes will be incorporated in new editions of the publication. IBM may
make improvements and/or changes in the product(s) and/or the program(s)
described in this publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.
Copyrights and Acknowledgments
Licensed Materials - Property of IBM
Copyright IBM Corp. 2006 All Rights Reserved.
US Government Users Restricted Rights - Use, duplication or disclosure
restricted by SGA ADP Schedule Contract with IBM Corp.
Supplemental Copyrights and Acknowledgments
The following Copyrights and Acknowledgments apply to various software
components included in IBM WebSphere Portlet Factory, but neither created
nor owned by IBM.
This offering is based on technology from the Eclipse Project (http://www.eclipse.org/).
This product includes software developed by the Apache Software Foundation
(http://www.apache.org).
Portions of this software provided by JDOM. Copyright (C) 2001 Brett McLaughlin
& Jason Hunter. All rights reserved.
Portions of this software provided by the membership of the XML-DEV mailing
list. You can obtain a copy of the SAX copyright status at http:// www.megginson.com
/SAX/.
The following terms are trademarks of International Business Machines Corporation
in the United States, other countries, or both:
Cloudscape
IBM
Lotus
WebSphere
Workplace