[ https://issues.jboss.org/browse/TEIIDDES-2055?page=com.atlassian.jira.plu... ] Ted Jones edited comment on TEIIDDES-2055 at 2/17/14 4:49 PM: -------------------------------------------------------------- This is due to TeiidXmlImportSourcePage hard-coding the Content-Type on the HttpConnection to application/xml. The generated REST service sets the charset and so the 406 is thrown. Changing TeiidXmlImportSourcePage to use Content-Type=application/xml;charset=MacRoman (in my case) fixes this. This will be an issue for any REST service that specifies anything other than application/xml. We should allow the user to override the HTTP Headers in the importer. was (Author: tejones): This is due to TeiidXmlImportSourcePage hard-coding the Content-Type on the HttpConnection to application/xml. The generated REST service sets the charset and so the 406 is thrown. Changing TeiidXmlImportSourcePage to use Content-Type=application/xml;charset=MacRoman (in my case) fixes this. This will be an issue for any REST service that specifies We should allow the user to override the HTTP Headers in the importer. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira