| Summary | There are a number of schema types for strings that cannot contain certain characters. This must be considered when creating these. |
|---|---|
| Environment |
Artix 4.*, Artix 5.* |
| Question/Problem Description | Why does Artix throw an exception when using one of these types? anyURI, normalizedstring, token, language, Name, NCName, NMTOKEN or ID |
| Clarifying Information | |
| Error Message | Mon, 01 Jan 2013 11:22:33.0000000 [hostname.company.com:25012:119036832] (IT_BUS.FOUNDATION.AFC:0) I - IT_Bus::Exception: Invalid character or character sequence |
| Defect/Enhancement Number | |
| Cause | An attempt was made to create a string which does not conform to the schema specification for a type, for example a token is a string that does not contain line feeds, carriage returns, tabs, leading or trailing spaces, or multiple spaces. |
| Resolution |
Review the WSDL and schema documents to identify which of the schema types is being used and then search the source or original message to identify where this type is being instantiated and confirm that it conforms to the rules for that type. |
| Workaround | |
| Notes | |
| Attachment |
#Orbix
#KnowledgeDocs
