[
https://issues.jboss.org/browse/TEIID-3016?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-3016:
---------------------------------------
Since we are expected to set the headers as a map of string->list<string> it
would probably be easier for us to expect a json string for the headers, rather than
attempting to parse the header directly. So rather than,
{code}'ContentType=application/json;Accepts=application/text'{code}
{code}'{"ContentType":["application/json"],"Accepts":["application/text"]}'{code}
Add headers parameter to invokeHttp
-----------------------------------
Key: TEIID-3016
URL:
https://issues.jboss.org/browse/TEIID-3016
Project: Teiid
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: Misc. Connectors
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.8
There is a need to set common headers, such as content type and accepts. Since there may
be other custom values it probably makes sense to do this as a generic parameter as Ramesh
suggests:
call restBDM.invokeHttp(action => 'POST', endpoint => qp,
headers=>'ContentType=application/json;Accepts=application/text')
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)