[
https://issues.jboss.org/browse/TEIID-3520?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-3520:
-------------------------------------
There can couple different ways we can do this, one we can introduce a metadata property
on the SOAP and REST procedures to mark their invocation styles, then make decision based
on it. But even simpler, you can check if the WSDL URL is present or REST URL is present
on the WSConnection and make the decision on it. But introduce a rule that only one of the
WSDL URL or Swagger URL is present, not both on a given translator.
Extend the Swagger support in the WS Translator
-----------------------------------------------
Key: TEIID-3520
URL:
https://issues.jboss.org/browse/TEIID-3520
Project: Teiid
Issue Type: Feature Request
Components: Misc. Connectors
Reporter: Ramesh Reddy
Assignee: Kylin Soong
Fix For: 8.12
http://swagger.io is popular REST service description framework, it defines a
specification
http://swagger.io/specification/ for REST service definition.
Teiid WS translator should add the ability to read this file (like WSDL) and provide the
REST methods as endpoints that can be consumed from Teiid.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)