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.3.IF5 | CR74364 | SOAP Data Handler sets encodingStyle attribute on encoded element level only. (Applicable to SOAP 1.1, rpc/encoded payloads only) | Clients, which are not fully compatible with SOAP 1.1 specifications, may require the Body element of SOAP 1.1 messages to contain encodingStyle attribute. In order to do that, SOAP Config MO has a new property SetEncodingOn with possible values of Element (previous behavior, default) and Body. Please note that SOAP Data Handler will not explicitly disable encoding on the child elements in the case of the encodingStyle attribute set on the Body element, so compliance with SOAP 1.1 specifications will be Business Object dependent. | ||||
| 3.4.3.IF5 | CR74500 | Asynchronous outbound requests should fail if JMS provider error occurs. | Fixed. | ||||
| 3.4.3.IF5 | CR74502 | Upon JMS provider failure, adapter needs to clean-up resources and attempt to reconnect. | Fixed. | ||||
| 3.4.3.IF3 | CR83174/JR23062 |
SOAP Data Handler outputs empty elements during request processing. |
This behavior has been corrected to be consistent with previous versions of the data handler. Empty tags will not be generated for elements with null values, except in the case of a nillable element. |
||||
|
3.4.3.IF2 |
CR74454/JR22924 |
SOAP/JMS Handler does not terminate the adapter on JMS Exceptions. |
A new property TerminateOnJmsError, child of JNDI hierarchical property, has been introduced. Possible values are true, false(default). If the value of above property is set to true, any irresolvable JMS related exceptions encountered during request processing through soap/jms handler will result in adapter termination. |
||||
|
3.4.3.IF2 |
CR67791 |
There is no response payload trace in the event notification. |
Fixed. |
||||
|
3.4.3.IF1 |
CR59634 |
Failure in event processing of payloads resolving to Non-TLOs. |
Fixed. |
||||
|
3.4.3.IF1 |
CR67602/JR22577 |
During synchronous request processing, request is not failed when the adapter is unable to populate TLO response bo attribute. |
Fixed. |
||||
|
3.4.3 |
CR67572 |
Fatal error in parsing SOAP messages and XSD content in WSDL files due to incompatible version of XML/XSD parser in the classpath. |
Fixed by removing "%INSTALLEDDIR%"\connectors\WebServices\dependencies\j2ee.jar |
||||
|
3.4.3 |
CR67583/JR22528 |
During synchronous request processing, HTTP error responses with empty payloads are ignored by the adapter. |
Fixed. All error responses with empty payloads will result in failure of the originating request. |
||||
|
3.4.3 |
CR71832/JR22014 |
SOAP/HTTP(S) listeners fail redirected HTTP(S) requests. |
Problem background: According to HTTP 1.1 specifications (http://www.w3.org/Protocols/rfc2068/rfc2068), section 5.2, SOAP/HTTP(S) listener checks the correctness of host and port information specified in the request with host and port information of the listener itself. If there is a mismatch, the listener will stop processing the request and respond with a 400 (Bad Request) status code. Issue: When incoming requests are being routed by an enterprise gateway system in order to hide the end point, the host and port information of the request has to be changed before being sent to the SOAP/HTTP(S) listener (original request has host and port of the gateway). In some cases, such change is not supported by the gateway or is troublesome to implement in the gateway system. Solution: A new SOAP/HTTP(S) listener property has been introduced to solve the above issue. Please note that using this property to disable the validation of host and port information of the request, puts the SOAP/HTTP(S) listener out of compliance with HTTP 1.1 specification, section 5.2. Use of the new property should be restricted to the cases when an enterprise gateway system change is undesirable. To use this feature, add the following property to the SOAP/HTTP(S) Listener Property:
|
||||
|
3.4.3 |
CR71572/JR22015 |
Support Userid/Password authentication when establishing connection to JMS provider. |
Adapter for Web Services now supports two new properties
under JNDI hierarchical property: |
||||
|
3.4.3 |
CR71699/JR22016 |
The SOAP Data Handler appends new line after element opening tag; inconsistency with new line appearing for nil elements. |
Nil elements will not contain new lines after the opening
tags. |
||||
|
3.4.3 |
CR70984/JR21612 |
WSDL ODA does not recognize complex types derived by extensions in case when no additional elements are added to the extended complex type. |
Fixed. |
||||
|
3.4.3 |
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.3 |
CR29113/JR21611 |
WSDL ODA and SOAP Data Handler do not support nillable elements. |
A new ASI "nillable=true"
is now supported. |
||||
|
3.4.3 |
CR44131 |
WSDL ODA fails to display error message when it contains NULL (0x0000) character. |
Fixed. |
||||
|
3.4.3 |
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 |
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. |
Fixed. |
||||
|
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 %INSTALLEDDIR%/$INSTALLEDDIR) |
| 3.4.3.IF5 | WIN & UNIX | Replace the file | %INSTALLEDDIR%\DataHandlers\CwSOAPDataHandler.jar |
| 3.4.3.IF5 | WIN & UNIX | Replace the file | %INSTALLEDDIR%\connectors\WebServices\CWWebServices.jar |
|
3.4.3.IF3 |
WIN & UNIX |
Replace the file |
%INSTALLEDDIR%\DataHandlers\CwSOAPDataHandler.jar |
|
3.4.3.IF2 |
WIN & UNIX |
Replace the file |
%INSTALLEDDIR%\connectors\WebServices\CWWebServices.jar |
|
3.4.3.IF2 |
WIN & UNIX |
Replace the file |
%INSTALLEDDIR%\connectors\messages\WebServicesConnector.txt |
|
3.4.3.IF1 |
WIN & UNIX |
Replace the file |
%INSTALLEDDIR%\DataHandlers\CwSOAPDataHandler.jar |
|
3.4.3.IF1 |
WIN & UNIX |
Replace the file |
%INSTALLEDDIR%\connectors\WebServices\CWWebServices.jar |
|
3.4.3 |
WIN & UNIX |
Remove the file |
%INSTALLEDDIR%\connectors\WebServices\dependencies\j2ee.jar |
|
3.4.3 |
WIN & UNIX |
Replace the file |
%INSTALLEDDIR%\connectors\WebServices\CWWebServices.jar |
|
3.4.3 |
WIN & UNIX |
Replace the file |
%INSTALLEDDIR%\connectors\messages\WebServicesConnector.txt |
|
3.4.3 |
WIN & UNIX |
Replace the file |
%INSTALLEDDIR%\DataHandlers\CwSOAPDataHandler.jar |
|
3.4.3 |
WIN & UNIX |
Replace the file |
%INSTALLEDDIR%\ODA\WSDL\WSDLODA.jar |
|
3.4.2 |
WIN & UNIX |
Replace the file |
%INSTALLEDDIR%\ODA\WSDL\WSDLODA.jar |
|
3.4.1 |
WIN & UNIX |
Replace the file |
%INSTALLEDDIR%\connectors\WebServices\CWWebServices.jar |
|
3.4.1 |
WIN & UNIX |
Replace the file |
%INSTALLEDDIR%\DataHandlers\CwSOAPDataHandler.jar |
Feb 8th, 2006 2:00 AM
© 2006 IBM Corporation. Proprietary and Confidential. All Rights Reserved.