January 2019 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5639) Auto-generated REST war creates different context than Designer Generated REST war

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5639?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5639: --------------------------------------- [~dsteigne] I'd say this is an issue with Designer. The Teiid side is documented as expecting uri parameters in curly braces - http://teiid.github.io/teiid-documents/master/content/reference/REST_Serv... - which matches the jax rs specification. > Auto-generated REST war creates different context than Designer Generated REST war > ---------------------------------------------------------------------------------- > > Key: TEIID-5639 > URL: https://issues.jboss.org/browse/TEIID-5639 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.12.16.6_4 > 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&inC=def. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4051) Swagger metadata includes internal java constructs

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-4051?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4051: --------------------------------------- A related issue - https://github.com/swagger-api/swagger-codegen/issues/4831 It looks like the swagger utilities still don't understand StreamingOutput > Swagger metadata includes internal java constructs > -------------------------------------------------- > > Key: TEIID-4051 > URL: https://issues.jboss.org/browse/TEIID-4051 > Project: Teiid > Issue Type: Quality Risk > Components: Server > Affects Versions: 8.12.x > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.1 > > > From IntegrationTestRestWarGeneration the swagger metadata includes definitions for Statement, ResultSet, StreamingOutput, etc.: > ... > InputStream: > type: "object" > Statement: > type: "object" > properties: > queryTimeout: > type: "integer" > format: "int32" > closed: > type: "boolean" > default: false > resultSet: > $ref: "#/definitions/ResultSet" > ... -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5592) Update or deprecate teiid-quickstarts

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5592?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5592: --------------------------------------- The alternative is to deprecate - on the website and in the repo make it clear that it was written for older Teiids and JDV. > Update or deprecate teiid-quickstarts > ------------------------------------- > > Key: TEIID-5592 > URL: https://issues.jboss.org/browse/TEIID-5592 > Project: Teiid > Issue Type: Quality Risk > Components: Quick Starts > Reporter: Steven Hawkins > Assignee: Van Halbert > Priority: Major > Fix For: 12.1 > > > The last update to the quickstarts was for Teiid 10 - which should have been largely compatible with Teiid 11. However this should be reviewed and updated for Teiid 11 - or we should deprecate them and update teiid.io appropriately. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5640) Don't provide access to system schema over odata

by Steven Hawkins (Jira)

Steven Hawkins created TEIID-5640: ------------------------------------- Summary: Don't provide access to system schema over odata Key: TEIID-5640 URL: https://issues.jboss.org/browse/TEIID-5640 Project: Teiid Issue Type: Quality Risk Components: OData Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 12.1 We now create all of the edm metadata at once - including for system schema - but we should not allow that by default. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5639) Auto-generated REST war creates different context than Designer Generated REST war

by Debbie Steigner (Jira)

[ https://issues.jboss.org/browse/TEIID-5639?page=com.atlassian.jira.plugin... ] Debbie Steigner updated TEIID-5639: ----------------------------------- Attachment: WW-vdb.xml > Auto-generated REST war creates different context than Designer Generated REST war > ---------------------------------------------------------------------------------- > > Key: TEIID-5639 > URL: https://issues.jboss.org/browse/TEIID-5639 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.12.16.6_4 > 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&inC=def. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5639) Auto-generated REST war creates different context than Designer Generated REST war

by Debbie Steigner (Jira)

[ https://issues.jboss.org/browse/TEIID-5639?page=com.atlassian.jira.plugin... ] Debbie Steigner updated TEIID-5639: ----------------------------------- Attachment: AutoGenSwaggar.png > Auto-generated REST war creates different context than Designer Generated REST war > ---------------------------------------------------------------------------------- > > Key: TEIID-5639 > URL: https://issues.jboss.org/browse/TEIID-5639 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.12.16.6_4 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Priority: Major > Attachments: AutoGenSwaggar.png, DesignerGenSwagger.png > > > 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&inC=def. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5592) Update or deprecate teiid-quickstarts

by Van Halbert (Jira)

[ https://issues.jboss.org/browse/TEIID-5592?page=com.atlassian.jira.plugin... ] Van Halbert reassigned TEIID-5592: ---------------------------------- Assignee: Van Halbert (was: Steven Hawkins) > Update or deprecate teiid-quickstarts > ------------------------------------- > > Key: TEIID-5592 > URL: https://issues.jboss.org/browse/TEIID-5592 > Project: Teiid > Issue Type: Quality Risk > Components: Quick Starts > Reporter: Steven Hawkins > Assignee: Van Halbert > Priority: Major > Fix For: 12.1 > > > The last update to the quickstarts was for Teiid 10 - which should have been largely compatible with Teiid 11. However this should be reviewed and updated for Teiid 11 - or we should deprecate them and update teiid.io appropriately. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5639) Auto-generated REST war creates different context than Designer Generated REST war

by Debbie Steigner (Jira)

[ https://issues.jboss.org/browse/TEIID-5639?page=com.atlassian.jira.plugin... ] Debbie Steigner updated TEIID-5639: ----------------------------------- Attachment: DesignerGenSwagger.png > Auto-generated REST war creates different context than Designer Generated REST war > ---------------------------------------------------------------------------------- > > Key: TEIID-5639 > URL: https://issues.jboss.org/browse/TEIID-5639 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.12.16.6_4 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Priority: Major > Attachments: AutoGenSwaggar.png, DesignerGenSwagger.png > > > 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&inC=def. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5639) Auto-generated REST war creates different context than Designer Generated REST war

by Debbie Steigner (Jira)

Debbie Steigner created TEIID-5639: -------------------------------------- Summary: Auto-generated REST war creates different context than Designer Generated REST war Key: TEIID-5639 URL: https://issues.jboss.org/browse/TEIID-5639 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 8.12.16.6_4 Reporter: Debbie Steigner Assignee: Steven Hawkins Attachments: AutoGenSwaggar.png, DesignerGenSwagger.png 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&inC=def. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5638) Add Swagger UI location for auto-generated REST war in documentation

by Debbie Steigner (Jira)

Debbie Steigner created TEIID-5638: -------------------------------------- Summary: Add Swagger UI location for auto-generated REST war in documentation Key: TEIID-5638 URL: https://issues.jboss.org/browse/TEIID-5638 Project: Teiid Issue Type: Feature Request Components: Documentation Reporter: Debbie Steigner Assignee: Steven Hawkins When using the Designer generated REST war, Swagger UI is at http://localhost:8080/VDB but if using the auto-generated war file it is at http://localhost:8080/VDB_1/api. Can this be noted in the documentation? -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues January 2019