Resolution:
Description
==========
When processing and validating a document through BusinessConnect, it throws a validation error, even when the XML looks correct in a text editor, such as TextPad®

Environment
===========
TIBCO BusinessConnect  5.X

Cause
==========
By default, BC assumes all documents to be UTF-8 encoded. The reason that BC could not validate the document is because there is an illegal character (which does not conform to UTF-8 encoding). Some text editors assume that the document encoding is done in ISO-8859-1 (ASCII) or ANSI (Windows) and will display the document without error because the characters in question may be correct for that character set but not be UTF-8 compliant.

Resolution
==========
Make sure you view the document with an editor that can support UTF-8 characters.  The Notepad++ open source editor (available through SourceForge) is an example of an editor that has this feature.  

If the document is an XML document, you can set the character encoding as part of the prolog statement:  

<?xml version="1.0" encoding="ISO-8859-1"?>

This will instruct BC to validate the message with the correct character set.

BusinessConnect throws a validation error when the document looks OK in a text editor.How do I correct it?