The patch note contains the following sections:
This patch contains the following revisions since the last maintenance release:
| Available as of Version | CR Number | Data Handler | Description |
|---|---|---|---|
| 1.5.4 | *14874 | xml | The enhancement for CR13906 did not accommodate consecutive elements that are not present in the business object. |
| 1.5.3 | 14448 | edi | When constructing an edi X12 message from a request business object, the message counts contained in each SE segment are incorrectly cumulative of all preceding transactions rather than only the transactions within that specific transaction set. |
| 1.5.2 | 14049 | soap | Data Type inconsistency generated between WSGenUtility and SOAP Data Handler. |
| 1.5.2 | 14327 | soap | Added SOAP header support to the SOAP DataHandler |
| 1.5.1 | 13865 | xml | Xml data handler does not ignore child meta-objects when writing to an xml string |
| 1.5.1 | 13901 | xml | Recursive elements are not properly read when converting an xml string to a business object. |
| 1.5.1 | 13906 | xml | Xml data handler has been enhanced to ignore elements that are being read from an xml input stream, but do not exist in the business object definition. A new property, IgnoreUndefinedElements, has been added to the XML configuration meta-object. Possible values are "true" and "false". Setting this property to true forces the datahandler to ignore undefined elements when converting from xml to business object. Setting this property to false, or leaving it blank will cause the data handler to act as before; an error will be thrown when an undefined element is encountered in the xml input stream. |
| 1.5.1 | 13926 | xml | A new xml data handler
app-specific name-value pair, escape=true|false, was introduced in
data handler version 1.4.0. Since escape processing of all attributes has
significant performance overhead, the intent was to improve performance.
Unless an attribute explicitly contained escape=true in it's
app-specific info, it was not escape processed.
Because of the potential backward compatibility issues, this default behavior has been changed. As of this patch release, the absence of the escape app-specific info will cause the xml data handler to escape process that attribute. Additionally, the DefaultEscapeBehavior xml configuration meta-object attribute may be used to define the behavior of attributes which omit this app-specific info. For example, if your xml business objects contain many attributes but few of them require escape processing, it would be advisable to set DefaultEscapeBehavior to false, then add escape=true to the app-specific info of only those attributes which require escape processing. Conversely, if the majority of your attributes require escape processing, it would be advisable to set DefaultEscapeBehavior to true, then add escape=false to the app-specific info of only those attributes which do not require escape processing. |
*Because the next DataHandler release was code frozen at the time of this patch. This CR will not be resolved in DataHandler version 1.6.0
To perform an upgrade to this version of the Data Handler:
Add, replace, or remove the following files and directories as indicated:
| For Version | Platform | Add / Replace / Remove | File (Starting from %CROSSWORLDS%/$CROSSWORLDS) |
| All Versions | WIN/Solaris | Replace | DataHandlers\CwDataHandler.jar |
| All Versions | WIN/Solaris | Replace | repository\DataHandlers\MO_DataHandler_XML.txt |
June 14, 2002 11:37 AM
© 2002 IBM Corporation. Proprietary and Confidential. All Rights Reserved.