[
https://issues.jboss.org/browse/TEIID-4374?page=com.atlassian.jira.plugin...
]
Ramesh Reddy resolved TEIID-4374.
---------------------------------
Fix Version/s: 9.1
Resolution: Done
Labels: Beta1 (was: )
Luckily in this case your BODY was defined as Object type with simple parameters, so I
could inline individual properties as parameters to the procedure. If this was an Array
that would not be possible. I added the extra checking for this step.
I am not sure how the "apache.commons.io" dependency got introduced (must be
some version upgrade) but I added it to the dependencies list also, so that you do not
have to copy the module. (You should report these kind when you find them)
While testing this, it also uncovered couple issues with TEIID-2715 which I fixed on
master.
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
Labels: Beta1
Fix For: 9.1
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)