The patch note contains the following sections:
|
|
This patch contains the following revisions since the last maintenance release:
|
|
|||
|
Available as of Version |
CR Number/APAR# |
Feature |
Description |
| 3.4.2.1IF | CR70984/JR21612 | WSDL ODA does not recognize complex types derived by extensions in limited cases. | Fixed. |
| 3.4.2.1IF | CR62274/JR21338 | The SOAP Data Handler does not support n-cardinality SOAP Attributes on Simple Type Elements by using elem_value ASI. | Fixed. |
| 3.4.2.1IF | CR29113/JR21611 | WSDL ODA and SOAP Data Handler do not support nillable elements. | A new ASI "nillable=true" is now
supported. Nillable attributes are supported in Business Object to SOAP message transformations only. |
|
3.4.2.1IF |
CR44131 |
WSDL ODA fails to display error message when it contains special characters. |
Fixed. |
|
3.4.2.1IF |
CR61927/JR21187 |
WSDL ODA fails to resolve Business Objects types when complex types are defined in the separate inline schemas. |
Fix from 3.4.1.1IF merged with 3.4.2. |
|
3.4.2 |
CR61067 |
WSDL ODA fails to generate Business Objects when WSDL file contains bidirectional script characters. |
Fixed. |
|
3.4.1.1IF |
CR61927/JR21187 |
WSDL ODA fails to resolve Business Objects types when complex types are defined in the separate inline schemas. |
Fixed. |
|
3.4.1 |
CR47158/JR20556 |
The adapter appends new line to the beginning of the content returned from a call to a child data handler. |
SOAP Data Handler MO now supports new property UseNewLine with possible values of true/false. Value of true would add new line in the beginning of result obtained from a call to a child data handler; false would append the content right after the element opening tag. Default is true for backward compatibility.
Example: a. UseNewLine is set to true <ParentElement> content obtained from a child datahandler</ParentElement> b. UseNewLine is set to false <ParentElement>content obtained from a child datahandler</ParentElement> |
|
3.4.1 |
CR59943/JR20556 |
The SOAP/JMS protocol handler does not fail a request that has no response within configured ResponsetWaitTimeout value. |
|
|
3.4.1 |
CR60193 |
SOAP/HTTP(S) Handler ignores synchronous response payload if HTTP header Content-Length is not specified. |
Fixed. |
Add, replace, or remove the following files and directories as indicated below:
|
|
|||
|
For Connector Version |
Platform |
Add / Replace / Remove |
File (Starting from %CROSSWORLDS%/$CROSSWORLDS) |
|
3.4.2.1IF |
WIN & UNIX |
Replace the file |
%CROSSWORLDS%\DataHandlers\CwSOAPDataHandler.jar |
|
3.4.2.1IF |
WIN & UNIX |
Replace the file |
%CROSSWORLDS%\ODA\WSDL\WSDLODA.jar |
|
3.4.2 |
WIN & UNIX |
Replace the file |
%CROSSWORLDS%\ODA\WSDL\WSDLODA.jar |
|
3.4.1.1IF |
WIN & UNIX |
Replace the file |
%CROSSWORLDS%\ODA\WSDL\WSDLODA.jar |
|
3.4.1 |
WIN & UNIX |
Replace the file |
%CROSSWORLDS%\connectors\WebServices\CWWebServices.jar |
|
3.4.1 |
WIN & UNIX |
Replace the file |
%CROSSWORLDS%\DataHandlers\CwSOAPDataHandler.jar |
May 2nd, 2005 12:19 PM
© 2005 IBM Corporation. Proprietary and Confidential. All Rights Reserved.