teiid-issues February 2019

teiid-issues@lists.jboss.org

1 participants
355 discussions

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

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-4051?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4051: ------------------------------------- Are you trying to link this JIRA somehow with the TEIID-5555? > 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)

7 years, 2 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: --------------------------------------- I can confirm the StreamingOutput issue still happens with swagger 1.5.21 (we are currently at 1.5.17). Additionally the swagger produced by IntegrationTestRestWebserviceGeneration fails validation in editor.swagger.io: Schema error should have required property 'info' missingProperty: info Semantic error at paths./View/g1simplepost.post Operations with Parameters of "in: formData" must include "application/x-www-form-urlencoded" or "multipart/form-data" in their "consumes" property > 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)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4178) OData and Rest wars use different conventions

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-4178?page=com.atlassian.jira.plugin... ] Steven Hawkins reopened TEIID-4178: ----------------------------------- Reopening to make consistent - or at the very least ensure that version is optional for the rest path. > OData and Rest wars use different conventions > --------------------------------------------- > > Key: TEIID-4178 > URL: https://issues.jboss.org/browse/TEIID-4178 > Project: Teiid > Issue Type: Quality Risk > Components: OData, Server > Reporter: Steven Hawkins > Priority: Minor > Fix For: 12.1 > > > OData uses vdb.version while Rest uses vdb_version. If we were to make them the same, there would still need to be a backwards compatibility mode. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4178) OData and Rest wars use different conventions

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-4178?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4178: ---------------------------------- Fix Version/s: 12.1 (was: 10.0) > OData and Rest wars use different conventions > --------------------------------------------- > > Key: TEIID-4178 > URL: https://issues.jboss.org/browse/TEIID-4178 > Project: Teiid > Issue Type: Quality Risk > Components: OData, Server > Reporter: Steven Hawkins > Priority: Minor > Fix For: 12.1 > > > OData uses vdb.version while Rest uses vdb_version. If we were to make them the same, there would still need to be a backwards compatibility mode. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5641) Wrong Log Context in SYSADMIN.sql

by Mark Tawk (Jira)

Mark Tawk created TEIID-5641: -------------------------------- Summary: Wrong Log Context in SYSADMIN.sql Key: TEIID-5641 URL: https://issues.jboss.org/browse/TEIID-5641 Project: Teiid Issue Type: Bug Reporter: Mark Tawk Assignee: Steven Hawkins Some log contexts used in SYSADMIN.sql are not valid (org.teiid.MATVIEWS) or it should be org.teiid.PROCESSOR.MATVIEWS for example: _EXECUTE logMsg(context=>'org.teiid.MATVIEWS', level=>'WARN', msg=>e.exception);_ -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

← Newer
1
...
33
34
35
36
Older →

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues February 2019