IBM Support

WebSphere Adapter could not deal with control characters

Troubleshooting


Problem

WebSphere Adapter could not handle control characters in attributes with string type from business object.

Symptom

WebSphere Adapter fails to process the control character data, and the following RuntimeException is encountered.

java.lang.RuntimeException: An invalid XML character (Unicode: 0x13) was found in the element content

Cause

WebSphere Adapter builds the XML 1.0 file from the business object (BO) without checking the string type attributes for control characters. According to the XML 1.0 specification, some special characters are not supported. Refer to the following document for the range of characters that are discouraged.

http://www.w3.org/TR/REC-xml/#charsets

When the Adapter gets a BO from the application and builds the XML 1.0 file from this BO, the string type attributes are taken as they are. If there are control characters in the string, these control characters will be written into the XML 1.0 file even though they are deemed as illegal with the XML 1.0 specification. As a result the XML file may cause problems.

Resolving The Problem

Ensure that the business objects that are fed into WebSphere Adapter have valid content that comply with XML 1.0 specification. There should not be any control characters which are illegal with XML 1.0 in attributes with string type.

[{"Product":{"code":"SSMKUK","label":"WebSphere Adapters Family"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Adapter \u2013 Non-specific","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"7.0;6.2","Edition":"WebSphere","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
15 June 2018

UID

swg21422693

Page Feedback