May 2014 - teiid-designer-issues - Jboss List Archives

[JBoss JIRA] (TEIIDDES-2164) Editing teiid importer connection url can't be finished

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2164?page=com.atlassian.jira.plu... ] Matus Makovy updated TEIIDDES-2164: ----------------------------------- Summary: Editing teiid importer connection url can't be finished (was: Editing teiid importer connection url can't be finnished) > Editing teiid importer connection url can't be finished > ------------------------------------------------------- > > Key: TEIIDDES-2164 > URL: https://issues.jboss.org/browse/TEIIDDES-2164 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 8.3.2 > Reporter: Matus Makovy > Priority: Blocker > Attachments: bug.png > > > I have Teiid importer connection set up without authentication and when I try to edit its URL I get an error message "The User Name cannot be empty" (the same with password) but my connection doesn't need authentication, so I don't have any username or password. 'OK' button is disabled. > JBDS 7.1.1.GA + TeiidDesigner 8.3.2 -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2164) Editing teiid importer connection url can't be finnished

by Matus Makovy (JIRA)

Matus Makovy created TEIIDDES-2164: -------------------------------------- Summary: Editing teiid importer connection url can't be finnished Key: TEIIDDES-2164 URL: https://issues.jboss.org/browse/TEIIDDES-2164 Project: Teiid Designer Issue Type: Bug Affects Versions: 8.3.2 Reporter: Matus Makovy Priority: Blocker Attachments: bug.png I have Teiid importer connection set up without authentication and when I try to edit its URL I get an error message "The User Name cannot be empty" (the same with password) but my connection doesn't need authentication, so I don't have any username or password. 'OK' button is disabled. JBDS 7.1.1.GA + TeiidDesigner 8.3.2 -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2164) Editing teiid importer connection url can't be finnished

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2164?page=com.atlassian.jira.plu... ] Matus Makovy updated TEIIDDES-2164: ----------------------------------- Attachment: bug.png screenshot > Editing teiid importer connection url can't be finnished > -------------------------------------------------------- > > Key: TEIIDDES-2164 > URL: https://issues.jboss.org/browse/TEIIDDES-2164 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 8.3.2 > Reporter: Matus Makovy > Priority: Blocker > Attachments: bug.png > > > I have Teiid importer connection set up without authentication and when I try to edit its URL I get an error message "The User Name cannot be empty" (the same with password) but my connection doesn't need authentication, so I don't have any username or password. 'OK' button is disabled. > JBDS 7.1.1.GA + TeiidDesigner 8.3.2 -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2162) WSDL->Souce/View Importer issues

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2162?page=com.atlassian.jira.plu... ] Ted Jones reassigned TEIIDDES-2162: ----------------------------------- Assignee: Ted Jones > WSDL->Souce/View Importer issues > -------------------------------- > > Key: TEIIDDES-2162 > URL: https://issues.jboss.org/browse/TEIIDDES-2162 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.3.2 > Reporter: Ramesh Reddy > Assignee: Ted Jones > > For a demo I am looking for stock quote web service, and I found three of them > http://www.webservicex.net/stockquote.asmx?WSDL > http://www.restfulwebservices.net/wcf/StockQuoteService.svc?wsdl > http://ws.cdyne.com/delayedstockquote/delayedstockquote.asmx?WSDL > The first one I see that it is returning the CDATA section instead of result, I get that, the other two failed to finish the wizard for me. One did not let me form the response, another it said WSDL validation. > I tried all of them in SOAP-UI, and they worked to get results for me. I do think these are simple services that should have worked in Designer. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2163) REST based importer design is wrong

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2163?page=com.atlassian.jira.plu... ] Ted Jones resolved TEIIDDES-2163. --------------------------------- Resolution: Duplicate Issue This is covered by TEIIDDES-1829. > REST based importer design is wrong > ----------------------------------- > > Key: TEIIDDES-2163 > URL: https://issues.jboss.org/browse/TEIIDDES-2163 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.3.2 > Reporter: Ramesh Reddy > Priority: Critical > Attachments: RestFix.png > > > OK, I tried the REST based import wizard for the first time today since none of WSDL based solutions worked for me for those issues see TEIIDDES-2162 > I believe the REST based importer is designed to generate wrong artifacts. It was designed same as XML file, where a given XML file, Teiid designer aids the user to come up with a "view". The difference between a XML file and REST based service is, a > * REST service will have input parameters. It is the input parameters that makes it a service, otherwise it just a remote URL. > * REST Service can have optional paths > Take for example WSDL based SOAP importer also gets XML as result, but it is designed to produce a procedure to capture the input parameters and return tabular result. REST based service MUST be doing exact same thing. > Teiid invokeHTTP does work with relative and absolute URLs, Teiid even has "querystring" function https://docs.jboss.org/author/display/TEIID/BNF+for+SQL+Grammar#BNFforSQL... > to help build the query parameter part of the URL, then you just need to concat it with the URL to make the whole. > Then we also need give a way to build optional path, based on input parameter to procedure, so in reality a parameter can be part of path or parameter > IMO the way we have does not serve any real usecase, like mine where I was trying to read a quotes from REST service > http://ws.cdyne.com/delayedstockquote/delayedstockquote.asmx/GetQuickQuot... -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2080) Add Excel Datasource Extension metadata properties

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2080?page=com.atlassian.jira.plu... ] Paul Richardson resolved TEIIDDES-2080. --------------------------------------- Resolution: Out of Date As per comments, TEIIDDES-2094 renders this mute. > Add Excel Datasource Extension metadata properties > -------------------------------------------------- > > Key: TEIIDDES-2080 > URL: https://issues.jboss.org/browse/TEIIDDES-2080 > Project: Teiid Designer > Issue Type: Enhancement > Components: Import/Export > Reporter: Ramesh Reddy > Assignee: Paul Richardson > Fix For: 8.5 > > > Teiid 8.7 introducing Excel translator which is based on Apache POI https://issues.jboss.org/browse/TEIID-965. This translator defines some extension metadata for it to works correctly in Teiid Designer. See this document as to what are the properties and the name space and alias > https://docs.jboss.org/author/display/TEIID/Microsoft+Excel+Translator -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2147) Packaged runtime client lib versions in Designer are behind the corresponding server libs

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2147?page=com.atlassian.jira.plu... ] Paul Richardson closed TEIIDDES-2147. ------------------------------------- Resolution: Done > Packaged runtime client lib versions in Designer are behind the corresponding server libs > ----------------------------------------------------------------------------------------- > > Key: TEIIDDES-2147 > URL: https://issues.jboss.org/browse/TEIIDDES-2147 > Project: Teiid Designer > Issue Type: Bug > Components: Build > Affects Versions: 8.4, 8.5 > Reporter: Mark Drilling > Assignee: Paul Richardson > Fix For: 8.5 > > > See linked JIRA - TEIIDDES-2129. Running into issues where our cli calls hang when connected from Designer 8.4/8.5 on windows. Further investigation of our runtime client plugin shows that our packaged libs are not in sync with the corresponding server libs. > jboss-remoting - (Designer has v 3.2.3.GA) - (DV6 server has v3.2.16.GA) > xnio - (Designer has v 3.0.3 GA) - (DV6 server has 3.0.7GA) > We need to ensure our client versions are correct. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2094) Support for dynamic extension metadata

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2094?page=com.atlassian.jira.plu... ] Paul Richardson closed TEIIDDES-2094. ------------------------------------- Resolution: Done > Support for dynamic extension metadata > --------------------------------------- > > Key: TEIIDDES-2094 > URL: https://issues.jboss.org/browse/TEIIDDES-2094 > Project: Teiid Designer > Issue Type: Enhancement > Components: Import/Export > Reporter: Ramesh Reddy > Assignee: Paul Richardson > Priority: Critical > Fix For: 8.5 > > > Currently when Teiid core implements a new translator or customer/user implements a custom translator that has extension metadata, before they can use the translator in Designer to do some modeling, they need to define MED and register it. > With completion of TEIID-2904, in Teiid 8.7, a Admin api method can be used to interrogate the extension metadata properties defined for a translator. > Currently if user uses Teiid Connection importer with any new translator, it ignores all the extension metadata properties and removes them from the returned DDL that Designer did not recognize. That is really bad for custom connectors, because the VDB will not work properly once it is deployed back to Teiid Server. > I propose to devise a way to generate a dynamic MED for the purposes of current metadata import of the source and use it during the import and not ignore those extension metadata properties. > Depending upon implementation detail, we can also read the translators and their extension metadata support during the initial connection time and create all the required MEDs and register them. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2163) REST based importer design is wrong

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2163?page=com.atlassian.jira.plu... ] Ramesh Reddy updated TEIIDDES-2163: ----------------------------------- Description: OK, I tried the REST based import wizard for the first time today since none of WSDL based solutions worked for me for those issues see TEIIDDES-2162 I believe the REST based importer is designed to generate wrong artifacts. It was designed same as XML file, where a given XML file, Teiid designer aids the user to come up with a "view". The difference between a XML file and REST based service is, a * REST service will have input parameters. It is the input parameters that makes it a service, otherwise it just a remote URL. * REST Service can have optional paths Take for example WSDL based SOAP importer also gets XML as result, but it is designed to produce a procedure to capture the input parameters and return tabular result. REST based service MUST be doing exact same thing. Teiid invokeHTTP does work with relative and absolute URLs, Teiid even has "querystring" function https://docs.jboss.org/author/display/TEIID/BNF+for+SQL+Grammar#BNFforSQL... to help build the query parameter part of the URL, then you just need to concat it with the URL to make the whole. Then we also need give a way to build optional path, based on input parameter to procedure, so in reality a parameter can be part of path or parameter IMO the way we have does not serve any real usecase, like mine where I was trying to read a quotes from REST service http://ws.cdyne.com/delayedstockquote/delayedstockquote.asmx/GetQuickQuot... was: OK, I tried the REST based import wizard for the first time today since none of WSDL based solutions worked for me for those issues see TEIIDDES-2162 I believe the REST based importer is designed to generate wrong artifacts. It was designed same as XML file, where a given XML file, Teiid designer aids the user to come up with a "view". The difference between a XML file and REST based service is, a REST service will have input parameters. It is the input parameters that makes it a service, otherwise it just a remote URL. Take for example WSDL based SOAP importer also gets XML as result, but it is designed to produce a procedure to capture the input parameters and return tabular result. REST based service MUST be doing exact same thing. Teiid invokeHTTP does work with relative and absolute URLs, Teiid even has "querystring" function https://docs.jboss.org/author/display/TEIID/BNF+for+SQL+Grammar#BNFforSQL... to help build the query parameter part of the URL, then you just need to concat it with the URL to make the whole. IMO the way we have does not serve any real usecase, like mine where I was trying to read a quotes from REST service http://ws.cdyne.com/delayedstockquote/delayedstockquote.asmx/GetQuickQuot... > REST based importer design is wrong > ----------------------------------- > > Key: TEIIDDES-2163 > URL: https://issues.jboss.org/browse/TEIIDDES-2163 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.3.2 > Reporter: Ramesh Reddy > Priority: Critical > Attachments: RestFix.png > > > OK, I tried the REST based import wizard for the first time today since none of WSDL based solutions worked for me for those issues see TEIIDDES-2162 > I believe the REST based importer is designed to generate wrong artifacts. It was designed same as XML file, where a given XML file, Teiid designer aids the user to come up with a "view". The difference between a XML file and REST based service is, a > * REST service will have input parameters. It is the input parameters that makes it a service, otherwise it just a remote URL. > * REST Service can have optional paths > Take for example WSDL based SOAP importer also gets XML as result, but it is designed to produce a procedure to capture the input parameters and return tabular result. REST based service MUST be doing exact same thing. > Teiid invokeHTTP does work with relative and absolute URLs, Teiid even has "querystring" function https://docs.jboss.org/author/display/TEIID/BNF+for+SQL+Grammar#BNFforSQL... > to help build the query parameter part of the URL, then you just need to concat it with the URL to make the whole. > Then we also need give a way to build optional path, based on input parameter to procedure, so in reality a parameter can be part of path or parameter > IMO the way we have does not serve any real usecase, like mine where I was trying to read a quotes from REST service > http://ws.cdyne.com/delayedstockquote/delayedstockquote.asmx/GetQuickQuot... -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2163) REST based importer design is wrong

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2163?page=com.atlassian.jira.plu... ] Ramesh Reddy updated TEIIDDES-2163: ----------------------------------- Attachment: RestFix.png {code} CREATE VIRTUAL PROCEDURE BEGIN DECLARE STRING VARIABLES.qp = QUERYSTRING('http://ws.cdyne.com/delayedstockquote/delayedstockquote.asmx/GetQuickQuote', ViewModel.getStockPrice.symbol AS StockSymbol, 0 AS LicenseKey); SELECT A.price AS price FROM (EXEC SourceModel.invokeHttp('GET', null, VARIABLES.qp, 'TRUE')) AS f, XMLTABLE(XMLNAMESPACES(DEFAULT 'http://ws.cdyne.com/'), '/decimal' PASSING XMLPARSE(DOCUMENT f.result) COLUMNS price double PATH 'text()') AS A; END {code} > REST based importer design is wrong > ----------------------------------- > > Key: TEIIDDES-2163 > URL: https://issues.jboss.org/browse/TEIIDDES-2163 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.3.2 > Reporter: Ramesh Reddy > Priority: Critical > Attachments: RestFix.png > > > OK, I tried the REST based import wizard for the first time today since none of WSDL based solutions worked for me for those issues see TEIIDDES-2162 > I believe the REST based importer is designed to generate wrong artifacts. It was designed same as XML file, where a given XML file, Teiid designer aids the user to come up with a "view". The difference between a XML file and REST based service is, a REST service will have input parameters. It is the input parameters that makes it a service, otherwise it just a remote URL. > Take for example WSDL based SOAP importer also gets XML as result, but it is designed to produce a procedure to capture the input parameters and return tabular result. REST based service MUST be doing exact same thing. > Teiid invokeHTTP does work with relative and absolute URLs, Teiid even has "querystring" function https://docs.jboss.org/author/display/TEIID/BNF+for+SQL+Grammar#BNFforSQL... > to help build the query parameter part of the URL, then you just need to concat it with the URL to make the whole. > IMO the way we have does not serve any real usecase, like mine where I was trying to read a quotes from REST service > http://ws.cdyne.com/delayedstockquote/delayedstockquote.asmx/GetQuickQuot... -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 8 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues May 2014