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.4.1 | 13000 | edi | If an attribute in an EDIFACT composite segment is preceded by a number of attributes that contain CxIgnore, the leading segment separators are NOT included in the EDI message |
| 1.4.2 | 13609 | tpi_rnif | Modification of tpi_rnif data handler to allow use of custom name handler class. |
| 1.4.3 | 13865 | xml | Xml data handler does not ignore child meta-objects when writing to an xml string |
| 1.4.4 | 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. |
Note: Whenever possible, IBM CrossWorlds attempts to roll all patch fixes into the next available maintenance release. However, in this specific instance, DataHandler release 1.5.0 is currently code frozen so CRs13865 and 13926 will not be rolled into the next maintenance release. After the 1.5.0 DataHandler is released, a 1.5.1 patch will be delivered. The fix to CRs13865 and 13926 will also be rolled into 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 |
| 1.4.4 | WIN/Solaris | Replace | repository\DataHandlers\MO_DataHandler_XML.txt |
April 16, 2002 08:56 AM
© 2001 CrossWorlds Software, Inc. Proprietary and Confidential. All Rights Reserved.