lineNumber: 1; columnNumber: 121; An invalid XML character (Unicode: 0x10) was found in the element content of the document.]
at javax.xml.bind.helpers.AbstractUnmarshallerImpl.createUnmarshalException(AbstractUnmarshallerImpl.java:335)
at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.createUnmarshalException(UnmarshallerImpl.java:526)
at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal0(UnmarshallerImpl.java:223)
at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:189)
at javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal(AbstractUnmarshallerImpl.java:157)
at javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal(AbstractUnmarshallerImpl.java:125)
...
Even this problem can be solved at SQL request level replacing these characters by a valid char as something as:
SELECT Replace(COL1, char(16), '') ...It's also a problem of XML encoding so we can add a new feature to manage correctly control characters. A best practice is to replace control character by `\uFFFD` (see http://www.fileformat.info/info/unicode/char/fffd/index.htm). A replacement by a value as `` is not valid because it's an HTML entity and has no real signification in XML point of view.
SELECT Replace(COL1, char(16), '') ...