[
https://issues.jboss.org/browse/TEIID-4374?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-4374:
-------------------------------------
All actions can only take single body parameter in OData as parameter input. See
http://docs.oasis-open.org/odata/odata-json-format/v4.0/errata03/os/odata...
the support for the PATH based parameters for ACTION is not there, thus it can not handle
the executeOperation.
Two way to make it work is, either change BODY parameter to PATH, or remove the PATH
parameter in the Swagger's executeOperation method and fold that into BODY
parameter's schema.
I also need to give little more thought as to if there are anything else we can do to
support this?
Procedure missing for an OData metadata request to a Swagger VDB
----------------------------------------------------------------
Key: TEIID-4374
URL:
https://issues.jboss.org/browse/TEIID-4374
Project: Teiid
Issue Type: Bug
Components: Misc. Connectors
Affects Versions: 9.0, 9.0.1, 9.0.2
Environment: Windows 10 Pro x64
Java 8
Reporter: Van Dillon
Assignee: Ramesh Reddy
Attachments: resource-adapter-rhq.xml, rhq-metadata.xml, rhq-vdb.xml,
swagger.json
When a REST PUT path defined in Swagger has a path parameter and a body it does not
appear in OData metadata.
See the attached swagger.json for an example. The operation 'executeOperation'
does not appear in OData metadata.
The code that determines if a procedure is allowed is in:
org.teiid.olingo.service.ODataSchemaBuilder.allowedProcedure()
The comment seems to indicate that as long as there is only a single LOB, multiple
'in' parameters are allowed. But the actual code does not allow any other
'in' parameters if there is a LOB parameter.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)