IBM WebSphere Integration Developer Fix Pack 6.0.1.1

for WebSphere Integration Developer 6.0.1

Welcome to IBM^® WebSphere^® Integration Developer fix pack 6.0.1.1 for WebSphere Integration Developer 6.0.1.

1.0 Prerequisites
2.0 Product fix history
3.0 Customer support
4.0 Notices and trademarks

1.0 Prerequisites

You must install IBM WebSphere Integration Developer 6.0.1 before installing the fix pack.

2.0 Product fix history

This fix pack contains many corrections and a few additions to WebSphere Integration Developer 6.0.1.

The following list is an overview of the components that have been updated and a description of some of the more significant problems addressed by the fix pack. There have been many minor user interface corrections to nearly all wizards and editors. There have also been numerous but minor documentation corrections. These minor corrections are not listed in detail here, though if there were a significant user interface or documentation update in a particular component, it is noted.

Assembly editor: Working with Web Service Definition Language (WSDL) files with different port type styles (for example, document literal wrapped and Remote Procedure Call (RPC)) could result in erroneous pop-up messages. The problem has been addressed. A null pointer exception could be returned when a component with a reference wired to an import was present. The problem has been addressed. When dropping a Java application to the assembly editor, a choice appeared to create an import or export rather than creating the expected Java component. The problem has been fixed. Deleting an interface in the assembly editor could sometimes delete more wires to a target component than expected. A correction has been made. Erroneous messages could appear not linked to the actions a user was performing. A correction has been made.
Business object editor: A null pointer exception could be thrown when creating a business object in a module with a ClearCase SCM adapter. The problem has been fixed. Opening a large XSD file with business objects could lead to a performance degradation. The error has been addressed. Inline business objects are now supported by the business object editor. Closing the business object editor immediately after opening it caused exceptions to be thrown. The problem has been fixed. The table view exhibited some unexpected behavior such as permitting the editing of a value cell in a business object and failing to refresh when types were changed. A correction has been made. You can now use filtering on business objects (APAR JR23370).
Business object mapping editor: Changes to maps were not always saved correctly. The problem has been fixed (APAR JR23303). When a transformation operation was invoked between two attributes, one of which was empty and had a child relationship to the first, a failure could occur. The problem has been fixed (APAR JR22990). When attempting to change the assign transform rule details for a business object map, the value field could hide the value. Entering a value, you could discover the property tag was incorrect. This problem has been fixed (APAR JR23499).
Business process editor: If you used an existing interface WSDL file as an interface partner in the editor, incorrect errors were returned to the user. The problem has been fixed (APAR JR23353). Code assist for the 'this' keyword in Java has been improved to show correct proposals when using it (APAR JR23189). Changes to correlation sets now save correctly. Previously, a change in some properties could cause the correlation set to save incorrect values (APAR JR23502). When a user had an extension to a simple type, the base type was not displayed. For example, instead of seeing an expected type of string, the user would see nothing displayed. A correction has been made to show the expected type (APAR JR22888). Changing an operation with the human task editor could sometimes result in an incorrect update of the Business Process Execution Language (BPEL) file. The problem has been corrected (APAR JR23188). An assign activity now correctly indicates when a type is an array and does not allow a user to expand it. A user is limited to assign one array field to another array field but not individual elements in the array (APAR JR23304).
Business rules: Namespaces could under some circumstances not be treated correctly. For example, two business objects with the same name but in separate namespaces could result in unpredictable results. The problem has been addressed (APAR JR23506). A namespace name has been limited to 4000 characters as very long names are unsupported on some operating systems. The editor would sometimes fail to correctly note that an invocation input had not been set when creating a rule set. This problem has been corrected. If a rule group partner was created with the rule group editor, then deleted, another partner could not be selected. This error has been corrected.
Debugger: Setting a case breakpoint on a business process could lead to unpredictable behavior. A correction has been made (APAR JR23433). You will no longer see double break points where one should appear. Even though a BPEL thread could be finished, the debugger could still show it running in the debugger. The problem has been corrected. A step over or step out under some conditions could appear to hang. A correction has been made.
Documentation generator: Under some circumstances, the generated documentation contained the selected resource from the master file instead of the defined resource of the master file. The problem has been fixed. A WSDL file with multiple port types could generate documentation missing the graphic of any port type. A correction has been made. Performance has been improved for cases where many similar artifacts, such as many business objects, are contained in the module using the documentation generator. When generating a report for a module, sometimes too many data types appeared in the module overview. These extra data types were actually WSDL inline data types. A correction has been made to remove these extra data types. On the edit content page, the changed report type could appear in the resource list instead of the saved resource type. This problem has been fixed.
Event monitor: If you set an event on a parameter mediation in the case of an interface map with parameter mediations, then changed the mapping type, you could experience a performance degradation. The problem has been corrected. An event source could still list events for a Java interface even thought the Java interface has been deleted. The error has been corrected. An obsolete transaction option, None, has been removed from the event monitor. Switching to high contrast mode could result in the disappearance of table headings and labels. The error has been corrected. The events tab in the properties page for a Java snippet BPEL activity no longer contains the entry event.
Help updates: There have been numerous but small changes to the documentation to support the functional changes listed in this fix pack.
Importing and exporting EIS services: A null pointer exception could be thrown when trying to bind an import with a JMS binding. The problem has been corrected. Compilation errors occurred in generated code when namespaces containing Java keywords were converted to package names in Java. A correction has been made. COBOL items that contained Java reserved words caused compilation errors later when these items became the basis for generated Java code. The problem has been fixed. If you had several assembly diagrams open and then added JMS bindings to exports within them, you could discover that properties from one module were appearing in another module too. This defect has been addressed. Two additional properties, interaction style and asynchronous reliability, have been added for JMS and EIS export bindings. They provide greater flexibility for you when you create your export bindings. The JMS import binding and export binding dialog box has had some usability improvements.
Interface editor: If an operation had two port type styles, such as document literal for an input and RPC for an output, it could lead to an error as only one style would be used for the operation. This problem has been addressed. A null pointer exception was thrown by the interface editor when opening a document with a port type style of document literal and an anonymous type member. The error has been corrected. Simple data types for an input or output could only be selected through the properties view; they did not appear in the interface editor. This problem has been corrected. Interface dependencies on artifacts would appear as grey text in the reference view as if the artifacts were unresolved, even though these artifacts were legitimate references. A correction has been made. You can now open a WSDL file with no port type. You can not take advantage of method overloading on a component within the same interface. This means that if you did create duplicate methods and removed one of them from a component implementation to rid yourself of a compilation editor, the Java validators throw another error. This error has been fixed (APAR JR23474).
Mediation flow editor: If you opened a mediation flow editor on an existing mediation flow and selected an operation wire, it still could request that you select a source operation
to define the mediation flow. This defect has been fixed. Creating custom mediation primitives with a mix of visual code and Java code in the implementation of the primitives could result in losing the Java code. A fix has corrected the problem. Modules and mediation modules could get mixed up if you created a mediation module, deleted it at the file system level, and then created a module with the same name. This error has been fixed. In the XSLT primitive, selecting the browse button would launch a page without a title. A title has been added. A mediation flow that is brought into the assembly editor could result in errors indicating that references do not match. This problem has been fixed.
Migration: A limitation of 4000 characters for a namespace length has been specified. If in a WebSphere Studio Application Developer Integration Edition application you had a partner link type defined more than once then with the same name, then on migration you would receive an error message that was empty.
Relationship editor: A null pointer exception could be thrown if a file without an extension is deleted. Typically, this would occur if you switched to the physical resources view and create a file without specifying an extension. The problem has been corrected. Business objects in a library might not have been visible inside the add role selection list. This problem has been corrected. After you have used the documentation generator, the relationship editor could stop working. This problem has been fixed.
Samples and tutorials: A correction was made to the mediation flow editor sample. Several other samples had minor text changes.
Selector editor: When an operation was selected and the selection criteria switched to Java, then clicking the Java snippet would create errors. This problem has been fixed (APAR JR23151). If you deleted a port type, which is part of the interface for
a selector, you needed to delete each operation definition in the port type separately. For example, if you have 50 operations you would need to delete 50 times. This problem has been fixed.
State machine editor: If you had several states and transitions and created a composite state for them, edge transitions and their transitions were lost. The problem has been fixed. Double-byte characters could cause opening a state machine in the assembly editor to fail. The problem has been corrected.
Test client: The component test user interface will now populate default values for elements automatically if you have default values specified in a business object XSD type (APAR JR23124). When you saved a list containing a complex type which also contained a complex type to the data pool, later you would find that all the fields were set to 0 even though non-zero values were presented when saved. This error has been fixed. You can now remove a value in the data pool editor when multiple selections have been made. Shortcut keys for copy and paste such as ctrl-v, ctrl-c, and ctrl-x now will work in the component tester.
Visual snippet editor: The visual snippet for activityInstance() found in the properties generated incorrect code. A correction has been made (APAR JR23482). A simple type's name and namespace could fail to match in the generated code. This error has been fixed (APAR JR23197). A visual Java snippet generated wrong code for a method with no return value. This problem has been fixed (APAR JR23115). Copying and pasting activities in situations with multiple and nested case and switch statements could result in a null pointer exception. This problem has been fixed.

To see a list of previous fixes included in this fix pack, click here.

3.0 Customer support

The product home page for WebSphere Integration Developer is www.ibm.com/software/integration/wid/. For FAQs, lists of known problems and fixes, and other support information, visit the Support page on the product home page.

4.0 Notices and trademarks

© Copyright IBM Corporation 2000, 2006. All Rights Reserved.

The XDoclet Documentation included in this IBM product is used with permission and is covered under the following copyright attribution statement: Copyright © 2000-2006, XDoclet Team. All rights reserved.

Portions based on Design Patterns: Elements of Reusable Object-Oriented Software, by Erich Gamma, Richard Helm, Ralph Johnson and John Vlissides, Copyright © 1995 by Addison-Wesley Publishing Company, Inc. All rights reserved.

U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

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 documentation 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 documentation. The furnishing of this documentation does not give 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, 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 OR CONDITIONS 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.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:

Intellectual Property Dept. for Rational Software
IBM Corporation
3600 Steeles Avenue East
Markham, Ontario
Canada L3R 9Z7

Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.

The licensed program described in this documentation and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

This information contains sample application programs in source language, which illustrates programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs.

Each copy or any portion of these sample programs or any derivative work, must include a copyright notice as follows:

If you are viewing a soft copy of this information, the photographs and color illustrations may not appear.

Programming interface information

Programming interface information is intended to help you create application software using this program.

General-use programming interfaces allow you to write application software that obtain the services of this program's tools.

However, this information may also contain diagnosis, modification, and tuning information. Diagnosis, modification, and tuning information is provided to help you debug your application software.

Warning: Do not use this diagnosis, modification, and tuning information as a programming interface because it is subject to change.

Trademarks and service marks

See www.ibm.com/legal/copytrade.shtml.

Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.