March 2015 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2422) XSD model created in wrong folder when creating Web service model from WSDL

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2422?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2422: ----------------------------------- Fix Version/s: 9.0.2 Beta1 > XSD model created in wrong folder when creating Web service model from WSDL > --------------------------------------------------------------------------- > > Key: TEIIDDES-2422 > URL: https://issues.jboss.org/browse/TEIIDDES-2422 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Reporter: Andrej Šmigala > Assignee: Ted Jones > Priority: Minor > Fix For: 9.1, 9.0.2 Beta1, 9.0.2 > > > When creating a Web Service model from an existing WSDL, there is an option to change the target location of the imported xml schema. Changing this location however results in the schema model being created in the wrong folder. > Expected result: > The XML and Web Service models are created in the 'web_services' subfolder, the XSD model is created in the 'schemas' subfolder. > Actual result: > The XML and Web Service models are created in the 'web_services' subfolder, but the XSD model is created in 'web_services/schemas' subfolder. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2422) XSD model created in wrong folder when creating Web service model from WSDL

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2422?page=com.atlassian.jira.plu... ] Ted Jones updated TEIIDDES-2422: -------------------------------- Git Pull Request: https://github.com/Teiid-Designer/teiid-designer/pull/438 > XSD model created in wrong folder when creating Web service model from WSDL > --------------------------------------------------------------------------- > > Key: TEIIDDES-2422 > URL: https://issues.jboss.org/browse/TEIIDDES-2422 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Reporter: Andrej Šmigala > Assignee: Ted Jones > Priority: Minor > Fix For: 9.1, 9.0.2 > > > When creating a Web Service model from an existing WSDL, there is an option to change the target location of the imported xml schema. Changing this location however results in the schema model being created in the wrong folder. > Expected result: > The XML and Web Service models are created in the 'web_services' subfolder, the XSD model is created in the 'schemas' subfolder. > Actual result: > The XML and Web Service models are created in the 'web_services' subfolder, but the XSD model is created in 'web_services/schemas' subfolder. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2463) Add feature to refresh virtual model from source model

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2463?page=com.atlassian.jira.plu... ] Van Halbert commented on TEIIDDES-2463: --------------------------------------- The initial capability is what designer does when you create new virtual model and select to transform from source. So it would be no difference. As for impact analysis, is anything additional being done before Komodo? > Add feature to refresh virtual model from source model > ------------------------------------------------------ > > Key: TEIIDDES-2463 > URL: https://issues.jboss.org/browse/TEIIDDES-2463 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling > Affects Versions: 9.0 > Reporter: Van Halbert > > Our design philosophy has been to create a virtual layer (i'll refer to as layer1) on top of the source model (1-for-1) so that as changes are made to the data source, they don't impact the out-side-layer (Data Access Layer) the client apps use. Which is part of the reason why layering of models works. > So the enhancement is to add the ability to refresh a view model from the source model. Example. 1st time layer1 is created (transformed) from source, all views are included. And down the road, the data source adds new tables (or in layer1 model, views had been removed). Now you want to refresh the layer1 model. Add an option to add in (transform) any missing tables, as was done when the layer1 model was originally created. So that the user doesn't have to manually figure out what's new and add them one-at-a-time. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2463) Add feature to refresh virtual model from source model

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2463?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2463: ---------------------------------------- Any initial capability would be simple SELECT * FROM XXXXXX transformation. However, is the simple virtual layer with pass-through for their sources a common use-case? What are the benefits for doing so? I think time would be better spent addressing and creating better impact analysis functionality when source schema changes. > Add feature to refresh virtual model from source model > ------------------------------------------------------ > > Key: TEIIDDES-2463 > URL: https://issues.jboss.org/browse/TEIIDDES-2463 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling > Affects Versions: 9.0 > Reporter: Van Halbert > > Our design philosophy has been to create a virtual layer (i'll refer to as layer1) on top of the source model (1-for-1) so that as changes are made to the data source, they don't impact the out-side-layer (Data Access Layer) the client apps use. Which is part of the reason why layering of models works. > So the enhancement is to add the ability to refresh a view model from the source model. Example. 1st time layer1 is created (transformed) from source, all views are included. And down the road, the data source adds new tables (or in layer1 model, views had been removed). Now you want to refresh the layer1 model. Add an option to add in (transform) any missing tables, as was done when the layer1 model was originally created. So that the user doesn't have to manually figure out what's new and add them one-at-a-time. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2463) Add feature to refresh virtual model from source model

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2463?page=com.atlassian.jira.plu... ] Van Halbert updated TEIIDDES-2463: ---------------------------------- Description: Our design philosophy has been to create a virtual layer (i'll refer to as layer1) on top of the source model (1-for-1) so that as changes are made to the data source, they don't impact the out-side-layer (Data Access Layer) the client apps use. Which is part of the reason why layering of models works. So the enhancement is to add the ability to refresh a view model from the source model. Example. 1st time layer1 is created (transformed) from source, all views are included. And down the road, the data source adds new tables (or in layer1 model, views had been removed). Now you want to refresh the layer1 model. Add an option to add in (transform) any missing tables, as was done when the layer1 model was originally created. So that the user doesn't have to manually figure out what's new and add them one-at-a-time. was: Our design philosophy has been to create a virtual layer (i'll refer to as layer1) on top of the source model (1-for-1) so that as changes are made to the data source, they don't impact the out-side-layer (Data Access Layer) the client apps use. Which is part of the reason why layering of models works. Then enhancement is add the ability to refresh a view model from the source model. Example. 1st time layer1 is created (transformed) from source, all views are included. And down the road, the data source adds new tables (or in layer1 model, views had been removed). Now you want to refresh the layer1 model. Add an option to add in (transform) any missing tables, as was done when the layer1 model was originally created. So that the user doesn't have to manually figure out what's new and add them one-at-a-time. > Add feature to refresh virtual model from source model > ------------------------------------------------------ > > Key: TEIIDDES-2463 > URL: https://issues.jboss.org/browse/TEIIDDES-2463 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling > Affects Versions: 9.0 > Reporter: Van Halbert > > Our design philosophy has been to create a virtual layer (i'll refer to as layer1) on top of the source model (1-for-1) so that as changes are made to the data source, they don't impact the out-side-layer (Data Access Layer) the client apps use. Which is part of the reason why layering of models works. > So the enhancement is to add the ability to refresh a view model from the source model. Example. 1st time layer1 is created (transformed) from source, all views are included. And down the road, the data source adds new tables (or in layer1 model, views had been removed). Now you want to refresh the layer1 model. Add an option to add in (transform) any missing tables, as was done when the layer1 model was originally created. So that the user doesn't have to manually figure out what's new and add them one-at-a-time. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2463) Add feature to refresh virtual model from source model

by Van Halbert (JIRA)

Van Halbert created TEIIDDES-2463: ------------------------------------- Summary: Add feature to refresh virtual model from source model Key: TEIIDDES-2463 URL: https://issues.jboss.org/browse/TEIIDDES-2463 Project: Teiid Designer Issue Type: Feature Request Components: Modeling Affects Versions: 9.0 Reporter: Van Halbert Our design philosophy has been to create a virtual layer (i'll refer to as layer1) on top of the source model (1-for-1) so that as changes are made to the data source, they don't impact the out-side-layer (Data Access Layer) the client apps use. Which is part of the reason why layering of models works. Then enhancement is add the ability to refresh a view model from the source model. Example. 1st time layer1 is created (transformed) from source, all views are included. And down the road, the data source adds new tables (or in layer1 model, views had been removed). Now you want to refresh the layer1 model. Add an option to add in (transform) any missing tables, as was done when the layer1 model was originally created. So that the user doesn't have to manually figure out what's new and add them one-at-a-time. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2439) Import from JSON error not helpful

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2439?page=com.atlassian.jira.plu... ] Barry LaFond reopened TEIIDDES-2439: ------------------------------------ commit not yet applied to master for 9.1 release > Import from JSON error not helpful > ---------------------------------- > > Key: TEIIDDES-2439 > URL: https://issues.jboss.org/browse/TEIIDDES-2439 > Project: Teiid Designer > Issue Type: Quality Risk > Components: Import/Export > Affects Versions: 9.0.1 > Reporter: Steven Hawkins > Assignee: Ted Jones > Fix For: 9.1, 9.0.2 Beta1, 9.0.2 > > > When importing from a json document, occasionally people are using docs with multiple expressions. The exception shown seems like xml parsing is being used. It should be clearer or offer an option of which expression to use. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2439) Import from JSON error not helpful

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2439?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2439: ----------------------------------- Fix Version/s: 9.1 9.0.2 Beta1 > Import from JSON error not helpful > ---------------------------------- > > Key: TEIIDDES-2439 > URL: https://issues.jboss.org/browse/TEIIDDES-2439 > Project: Teiid Designer > Issue Type: Quality Risk > Components: Import/Export > Affects Versions: 9.0.1 > Reporter: Steven Hawkins > Assignee: Ted Jones > Fix For: 9.1, 9.0.2 Beta1, 9.0.2 > > > When importing from a json document, occasionally people are using docs with multiple expressions. The exception shown seems like xml parsing is being used. It should be clearer or offer an option of which expression to use. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2457) REST (JSON) Importer Doesn't Distinguish Between Object and Array

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2457?page=com.atlassian.jira.plu... ] Barry LaFond reopened TEIIDDES-2457: ------------------------------------ Issue not yet committed to master for 9.1 release > REST (JSON) Importer Doesn't Distinguish Between Object and Array > ----------------------------------------------------------------- > > Key: TEIIDDES-2457 > URL: https://issues.jboss.org/browse/TEIIDDES-2457 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export, Web Services Support > Affects Versions: 9.0.1 > Reporter: Ted Jones > Assignee: Ted Jones > Fix For: 9.1, 9.0.2 > > > When importing JSON arrays, we should parse with JSONArray, not JSONObject. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2457) REST (JSON) Importer Doesn't Distinguish Between Object and Array

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2457?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2457: ----------------------------------- Fix Version/s: 9.0.2 Beta1 > REST (JSON) Importer Doesn't Distinguish Between Object and Array > ----------------------------------------------------------------- > > Key: TEIIDDES-2457 > URL: https://issues.jboss.org/browse/TEIIDDES-2457 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export, Web Services Support > Affects Versions: 9.0.1 > Reporter: Ted Jones > Assignee: Ted Jones > Fix For: 9.1, 9.0.2 Beta1, 9.0.2 > > > When importing JSON arrays, we should parse with JSONArray, not JSONObject. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 7 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 March 2015