[
https://issues.jboss.org/browse/TEIIDDES-3223?page=com.atlassian.jira.plu...
]
Ramesh Reddy commented on TEIIDDES-3223:
----------------------------------------
agree, the root of the context should never point to the swagger API. Swagger UI is just a
testing tool, should be on a separate path, but documented as there is no expectation from
end user that there is swagger UI, but working service at root.
Auto-generated REST war creates different context than Designer
Generated REST war
----------------------------------------------------------------------------------
Key: TEIIDDES-3223
URL:
https://issues.jboss.org/browse/TEIIDDES-3223
Project: Teiid Designer
Issue Type: Bug
Reporter: Debbie Steigner
Assignee: Steven Hawkins
Priority: Major
Attachments: AutoGenSwaggar.png, DesignerGenSwagger.png, WW-vdb.xml
Have a REST procedure with 3 optional parameters and have the REST:URI set to
testget&inA&inB&inC, the Designer Generated War takes the REST:URI of
testget&inA&inB&inC and drops the params, so you see in the Swagger UI the
operation is just /AAA/testget, so the Request URL is
http://localhost:8080/WW/AAA/testget?inA=abc&inC=def but the auto-generated war file
doesn't drop the params from the REST:URI and it shows as
/AAA/testget&inA&inB&inC so the actual Request URL would be
http://localhost:8080/WW_1/AAA/testget&inA&inB&inC?inA=abc&am....
--
This message was sent by Atlassian Jira
(v7.12.1#712002)