XML Data Handler 2.7.3 Fix Pack

Download Description

History of fixes

Version 2.7.3

72224
The XML ODA does not support MaxLength. Business object attributes default to a MaxLength value of 255 for simple attributes. The value of MaxLength Facets in the XML Schema should be detected for simple type definitions and be applied to corresponding attributes in business object definitions.

CR84569/JR24073
The XML ODA generates a string attribute instead of a child object. The XML ODA does not support nested complex type elements with simple content, where the simple content is defined to have extensions (the addition of one or more attributes).

CR85441
The XML Data Handler produces misleading messages during event processing. The following error message is sometimes seen while calling the Name Handler (to resolve the business object name): Error: BusinessObject Name cannot be determined from the DOCTYPE in the data stream.

This message is not always accurate or specific, because it can be caused by both a business object prefix that is not configured or by a mis-typed NameHandler class name.

CR68538/JR24368
During event processing, the XML Data Handler logs the message: Warning possible loss of data. This issue is very similar to CR84327 (detailed below).

CR49420/JR24339
The XML Data Handler fails to process XML data containing a byte order mark (BOM) during event processing. It is valid for an XML document to specify an encoding using a BOM.

CR84723/JR24206
The XML Data Handler does not determine the top level object name during event processing. The following message is logged: Cannot convert XML with root tag %XXX.YYY% to %BOName%..

CR84429/JR23994
The XML Data Handler fails with an exception indicating that no data attribute was found during event processing. A SAXException indicates there is "No data attribute for %XMLTag% in %BOName%." This error occurs while processing nested complex type (wrapper) elements and might require business object definitions to be generated again using the ODA. This is because business object level application-specific information for some business objects might indicate "type=MIXED," even though they are not mixed elements, "MIXED=true," as defined in the XSD file.

CR84327/JR24006
The XML Data Handler log indicates the possible loss of data during event processing. This is generally a valid warning message indicating the business object definition and XML structure do not match. It can occur when multiple elements reference the same complex type (extensions of simple content), a scenario that is not handled properly by the Data Handler.

CR74449/JR23245
During event processing, the XML Data Handler fails with an error stating that the attribute tag was not found. This failure occurs when the Data Handler processes nested complex type elements (for example, all or choice model group definitions).

Version 2.7.2

CR62002/JR22393
The XML ODA fails to generate business object definitions, resulting in a NullPointerException due to lack of nested AttributeGroup support.

CR62009/JR22392
The XML data handler does not preserve white space in simple tags.

CR67394 / JR22171
The XML data handler always performs escape processing (regardless of meta-object and application-specific information configuration) when converting from a business object to XML for business object attributes representing XML attributes.

CR71298 / JR22391
The XML data handler fails to convert an XML stream to a business object and responds with a NoSuchAttributeException message.  

CR71953 / JR21941
The XML data handler fails to process nested mixed type elements.

CR72301 / JR22390
The XML data handler assumes the Byte Order Mark has been removed in an XML response.
 
Only the "getBO(InputStream serializedData, Object config)" method supports XML content containing a BOM.

If the previously mentioned method is called, and the inputStream contains a recognized BOM, the method automatically invokes the setEncoding() method of the business object handler.

The standard polling method invoked by components (for example, JText adapter) is a getBO(Reader, …) method that assumes the BOM has been removed.

CR72730
The XML data handler is unable to process complex business objects and generates the following message:  “Formatting failed. Reason :: There is no attribute at position ‘-1’ in business object definition ‘XXXXXXX’.”

CR73328
The XML data handler fails to process documents with a top-level element value containing a hyphen ("-") character.   

Version 2.7.1

CR44470
The XML ODA might fail to generate business objects when a schema file imports other schemas. During business object generation, it returns the following message: "Error in call core.setAgentProperties: schema for type XXXXX not found." This condition occurs when a schema is imported into a different namespace where there is a reference to an element or complex type.