[teiid-issues] [JBoss JIRA] (TEIIDSB-134) OData 2 source fails with default headers
Steven Hawkins (Jira)
issues at jboss.org
Tue Nov 5 14:51:00 EST 2019
[ https://issues.jboss.org/browse/TEIIDSB-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steven Hawkins resolved TEIIDSB-134.
------------------------------------
Resolution: Done
Corrected the header logic to use all of the header values.
> OData 2 source fails with default headers
> -----------------------------------------
>
> Key: TEIIDSB-134
> URL: https://issues.jboss.org/browse/TEIIDSB-134
> Project: Teiid Spring Boot
> Issue Type: Bug
> Components: core, OData
> Affects Versions: 1.2.0
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 1.3.0
>
> Attachments: example-odata.zip
>
> Original Estimate: 3 minutes
> Remaining Estimate: 3 minutes
>
> The translator sets the content type by default: https://github.com/teiid/teiid/blob/06b9828a3fd6dafa358ff93f0a4803e69a3bfdf4/connectors/odata/translator-odata/src/main/java/org/teiid/translator/odata/BaseQueryExecution.java#L227
> This seems to be handled differently by CXF and spring webservice sources. A user is reporting that a simple request (without a payload) succeeds with CXF, but fails with spring.
> the translator throw org.springframework.web.client.HttpClientErrorException$UnsupportedMediaType: 415 Unsupported Media Type by executing Query, for example "Select * from categories", by jdbc client such as SQuirrel.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
More information about the teiid-issues
mailing list