[
https://issues.jboss.org/browse/TEIIDDES-3138?page=com.atlassian.jira.plu...
]
Steven Hawkins commented on TEIIDDES-3138:
------------------------------------------
invokeHttp(
action IN STRING,
request IN OBJECT,
endpoint IN STRING,
stream IN BOOLEAN,
result OUT BLOB,
contentType OUT STRING,
headers IN CLOB)
should be:
invokeHttp(
result OUT BLOB result,
action IN STRING,
request IN OBJECT,
endpoint IN STRING,
stream IN BOOLEAN,
contentType OUT STRING,
headers IN CLOB)
is expecting the result OUT BLOB to be the result set, so it's
not included as a parameter in the SQL?
OUT and result values do not need explicit parameters. Only if you are trying to capture
the OUT value to use a parameter, and it must be a variable. For result values you use
"var = call..."
Can I also assume that the EMF version of an invokeHttp() in a *.vdb
is ignored?
You mean the metadata declaration in the .xmi, yes. Only the index metadata is looked
at.
Designer is putting the return parameter in the wrong position on a
REST invokeHttp procedure
----------------------------------------------------------------------------------------------
Key: TEIIDDES-3138
URL:
https://issues.jboss.org/browse/TEIIDDES-3138
Project: Teiid Designer
Issue Type: Bug
Reporter: Debbie Steigner
Assignee: Barry LaFond
Designer is putting the return parameter in the wrong position on a REST invokeHttp
procedure. See
https://developer.jboss.org/message/977532 and
https://issues.jboss.org/browse/TEIID-5130
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)