IBM WebSphere Integration Developer 6.0.2 Interim Fix 003

for WebSphere Integration Developer 6.0.2

Welcome to IBM^® WebSphere^® Integration Developer 6.0.2 interim fix 003. It should be installed either on Linux or Windows. It contains the fixes described below.

Table of contents

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

1.0 Prerequisites

You must have installed IBM WebSphere Integration Developer 6.0.2.

2.0 Product fix history

This interim fix contains corrections to WebSphere Integration Developer 6.0.2.

This interim fix includes WebSphere Integration Developer 6.0.2 interim fix 001 and interim fix 002.

The following list describes the components that have been updated. APAR numbers, if applicable, are in parentheses.

• Adapters: This interim fix includes WebSphere Adapter for JDBC Version 6.0.2.1. 

  CR  / APAR number	CR details	Description of fix
  69043	A JDBC JCA with XA transaction, which also has a WebSphere Process Server DataSource, cannot connect to a local database.	The DataSource is now created with the adapter.
  87193	The execute operation on the Stored Procedure (SP) fails when the Stored Procedure has IN/OUT parameters.	Parameters of type IO are registered.
  87159	The adapter generates a ClassCastException exception for binary types within a stored procedure.	Binary types are handled properly for stored procedure parameters.
  87216	The JDBC adapter displays the length of the blob data, instead of the content of the blob data.	The adapter displays the blob data.

  The adapter support site contains more details. You will need to make some configuration changes as a result of updating the adapter RAR file. See Changes required after an adapter update.
• Assembly editor: A memory leak when using this editor has been corrected. In cases where imported projects contain many JAR files, there will be less annoying pop-up dialog boxes than previously.
• Business object editor: The Undo button could fail after using the Add attribute button. The problem has been fixed. Refactoring a business object name resulted in a stack trace printed to the log file. This error has been addressed.
• Business object mapping editor: Selecting a custom transformation of an imported business object map could result in seeing missing children of the business objects, when these attributes were in the imported files. This error has been addressed. Changing the namespace of a business object through refactoring created errors in an associated the business object map. The problem has been fixed. An invalid ASCII character could appear in a summary file. This problem has been addressed. After a referenced business object was deleted, a transform was still permitted for an attribute of the deleted business object. This error has been fixed.
• Business state machine editor: A business state machine based on a one-way interface could result in a disabled Finish button at generation time. The error has been fixed.
• Debugger: A business object map snippet would fail to appear in the debugger after a breakpoint had been reached. This problem has been corrected. 
• Documentation and samples: Some minor updates to the documentation include fixing links and adding an additional point to the What's New section of the Welcome view. Several corrections were made to the Loan Application sample and minor corrections to some others.
• Event monitor editor: Slow response times in this editor have been fixed. A memory leak with this editor has been corrected. Creating an invalid circular dependency failed to issue an error. This problem has been fixed. 
• Human task editor: A process instance of a human task could fail at runtime. The problem has been fixed. A necessary parameter failed to appear in the user interface with respect to staff settings. This problem has been addressed.
• Integration test client: In an emulation event, adding an element to a SOAP-encoded array resulted in a fault message. This problem has been fixed. This problem has been corrected. Adding an element to an array in a business object and setting the element to a null value resulted in a null pointer exception. This problem has been fixed. After an exception was thrown in a test case, no stop event occurred. This problem has been addressed. The integration test client also requires this runtime update to support these particular fixes. 
• Interface editor: Creating a web service binding on an import could result in an incorrect URL address in the interface. A correction has been made.
• Interface mapping editor: Generating an implementation of an interface map located in a subfolder of a module issued an error that the name of the interface was not a valid NCName. An NCName is a name that is not qualified with a namespace-related prefix. This problem has been addressed.
• Mediation flow editor: Adding a Message Element Setter primitive, which is used to set the content of message, to a mediation flow followed by adding an entry and selecting a type of copy resulted in a workbench failure. This error has been corrected. A mediation module in Linux displayed a business logic view rather than the mediation logic view. This problem has been fixed. When an XML Schema Definition (XSD) was imported and could not be resolved correctly, a null pointer exception was thrown. This problem has been fixed. Importing a Web service to be used with the mediation flow editor could cause a null pointer exception. This error has been fixed.
• Module deployment editor: A modified property value could not be saved if attempted several times. This problem has been corrected.
• Refactoring: Renaming the namespace of a business object could cause errors. This problem has been fixed. 
• Visual snippet editor: Creating an emitter snippet in a Java snippet activity would result in errors in the generated code. These errors have been corrected.
• WSDL importer and exporter: Importing a Web Services Description Language (WSDL) file in the Linux environment resulted in a null pointer exception. The problem has been fixed. Exporting a WSDL file using the merge function to create one WSDL file with inlined schemas could result in inconsistencies with the artifacts in the module where the export occurred. This problem has been fixed.
• Workspace name: An error would be issued in Windows if a workspace name entered by a user differed in case from the existing name. For example, C:\Workspace2 instead of c:\workspace2. This problem has been fixed.

Updates have been made to WebSphere Process Server and Rational Application Developer, both of which are included with WebSphere Integration Developer.  

3.0 Customer support

The product home page for WebSphere Integration Developer contains and references considerable information about the product. 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, 2007. 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-2007, 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  for WebSphere Integration Developer
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.

COPYRIGHT LICENSE:

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:

© (your company name) (year). Portions of this code are derived from IBM Corp. Sample Programs. © Copyright IBM Corp. 2000, 2007. All rights reserved.

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.