These release notes cover release information for version 2.4.0 of the XML data handler. They document any changes to the data handler contained in the file CwXMLDataHandler.jar (file version 2.4.0). These release notes contain the following sections:
New in this release | Installation, migration, upgrade, and configuration information |
Product fix history | Known problems and workarounds |
Hardware and software requirements | Documentation updates |
Note: Important information about this product may be available in Technical Support Flashes issued after these release notes were published. These can be found on the WebSphere Business Integration support Web site, http://www.ibm.com/websphere/integration/wbiserver/support. Select the component area of interest and search the flashes section.
This section lists the new features and improvements made in this release.
Refer to the Data Handler Guide for detailed information about the data handler.
Between releases 2.3.0 and 2.4.0, the following CRs, based on customer-reported cases, were fixed.
CR number | Description |
19973 | The XML ODA now includes a hash code in the business object names for XML elements defined as anonymous complex types. Fixed in Patch 2.3.1 |
21557 | The XML ODA displayed an incorrect description for the TopLevel property when the locale was set to Italian. |
22275 | The XML data handler, in certain cases, does not correctly read the InitialBufferSize property from the XML data handler meta-object. The property, which always defaults to 2 MB, can affect performance. Fixed in Patch 2.3.1 |
22807 | The XML ODA incorrectly marks business object attributes as isRequired in a choice wrapper. Fixed in Patch 2.3.2. |
22932 | The XML data handler fails in certain cases to parse nested elements with the same name when the elements are in a direct parent/child relationship. Fixed in Patch 2.3.3. |
Hardware and software requirements are included in the product documentation. See Installation, migration, upgrade, and configuration information for links to those guides.
Whether you are installing the software from the CD or downloading it from Passport Advantage and installing it from a local directory, refer to the appropriate guide:
These guides also include migration, upgrade, and configuration information.
As of the 2.2.0 release of WebSphere Business Integration Adapters, Business Object Designer no longer allows you to save a business object with the ObjectEventId attribute specified as a key. Because of this restriction, the XML ODA now sets the first attribute within all child business objects as the key, and sets no key attribute within the parent business object. To save your objects, you must analyze them first and set the appropriate attribute as a key. Failure to set an appropriate key attribute when using InterChange Server as the integration broker may have negative performance implications due to the event sequencing feature. Furthermore, because previous versions of the XML business object generation tools (XMLBorgen, Edifecs SpecBuilder, and XML ODA) set the ObjectEventId attribute as a key, you are strongly advised to review business objects that you are migrating from earlier WebSphere Business Integration Adapters systems and manually modify the key attribute using the Business Object Designer tool.
The following problems have been found in this release:
CR number | Description |
22443 | The XML data handler fails to parse an XML document that specifies a schema
document referring to external entities by including other schemas. Fixed
in Patch 2.3.1
Note: Whenever possible, IBM rolls all patch fixes into the next available maintenance release. However, this CR was not rolled into data handler version 2.4.0. If you require features of version 2.4.0 or the fix for this CR, contact IBM technical support and a 2.4.x patch will be sent to you. |
22773 | The XML data handler has the potential of
stalling when multiple threads are accessing and running the data
handler concurrently. This functionality was added in XML data handler
Fix Pack 2.3.4.
Note: Whenever possible, IBM rolls all patch fixes into the next available maintenance release. However, the 2.3.4 patch was not rolled into data handler version 2.4.0. If you require features of version 2.4.0 or the fix for this CR, contact IBM technical support and a 2.4.x patch will be sent to you. |
24220 |
When the notag application-specific information property exists on a business object attribute, a "notag" element tag is being generated on business-object-to-XML transformations. |
24223 | The XML data handler requires support for includes of schemas with no namespace. |
Product documentation is not included as part of the product package, either by CD or electronic product distribution. The documentation for this product can be found in the following InfoCenters:
http://www.ibm.com/websphere/integration/wicserver/infocenter
http://www.ibm.com/websphere/integration/wbiadapters/infocenter
To obtain the product documentation, visit the Web site and download the current documentation set for the release that you are using. Follow the instructions provided on the InfoCenter page to complete the installation.