April 2015 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2490) Salesforce importer imports tables under salesforce schema resulting in table names containing '.'

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2490?page=com.atlassian.jira.plu... ] Ramesh Reddy commented on TEIIDDES-2490: ---------------------------------------- Looking at issues with plural names etc, should we keep this importer as opposed to using Teiid Connection importer? > Salesforce importer imports tables under salesforce schema resulting in table names containing '.' > -------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2490 > URL: https://issues.jboss.org/browse/TEIIDDES-2490 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Reporter: Burak Serdar > Assignee: Mark Drilling > > Import salesforce data using salesforce importer, and deploy the VDB. The SYS.Tables table has table names of the form: > salesforce.Account > Third party tools that retrieve list of tables this way are not happy about the '.' in the table name. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2490) Salesforce importer imports tables under salesforce schema resulting in table names containing '.'

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2490?page=com.atlassian.jira.plu... ] Steven Hawkins moved TEIID-3430 to TEIIDDES-2490: ------------------------------------------------- Project: Teiid Designer (was: Teiid) Key: TEIIDDES-2490 (was: TEIID-3430) Component/s: Import/Export (was: Salesforce Connector) > Salesforce importer imports tables under salesforce schema resulting in table names containing '.' > -------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2490 > URL: https://issues.jboss.org/browse/TEIIDDES-2490 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Reporter: Burak Serdar > Assignee: Mark Drilling > > Import salesforce data using salesforce importer, and deploy the VDB. The SYS.Tables table has table names of the form: > salesforce.Account > Third party tools that retrieve list of tables this way are not happy about the '.' in the table name. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2489) Extra Root Path Value for JSON Array After Set as Root

by Ted Jones (JIRA)

Ted Jones created TEIIDDES-2489: ----------------------------------- Summary: Extra Root Path Value for JSON Array After Set as Root Key: TEIIDDES-2489 URL: https://issues.jboss.org/browse/TEIIDDES-2489 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 9.0.2 Reporter: Ted Jones Assignee: Ted Jones Fix For: 9.0.2 When importing a REST service that returns an array and setting the root path, an extra "response" node is added to the root path. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2434) Renaming issues - with folders inside project

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2434?page=com.atlassian.jira.plu... ] Mark Drilling reassigned TEIIDDES-2434: --------------------------------------- Assignee: Paul Richardson (was: Mark Drilling) > Renaming issues - with folders inside project > --------------------------------------------- > > Key: TEIIDDES-2434 > URL: https://issues.jboss.org/browse/TEIIDDES-2434 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 9.0.1 > Environment: Windows > Reporter: Matus Makovy > Assignee: Paul Richardson > Fix For: 9.1, 9.0.2 > > Attachments: renaming-source.png, TestRefactor.zip > > > More issues with renaming models. See steps to reproduce. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2434) Renaming issues - with folders inside project

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2434?page=com.atlassian.jira.plu... ] Mark Drilling commented on TEIIDDES-2434: ----------------------------------------- Submitted pull request for the rename problem on Windows OS - https://github.com/Teiid-Designer/teiid-designer/pull/447 Assigning to [~phantomjinx] to take a look at the scenario in my previous comment. > Renaming issues - with folders inside project > --------------------------------------------- > > Key: TEIIDDES-2434 > URL: https://issues.jboss.org/browse/TEIIDDES-2434 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 9.0.1 > Environment: Windows > Reporter: Matus Makovy > Assignee: Mark Drilling > Fix For: 9.1, 9.0.2 > > Attachments: renaming-source.png, TestRefactor.zip > > > More issues with renaming models. See steps to reproduce. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2434) Renaming issues - with folders inside project

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2434?page=com.atlassian.jira.plu... ] Mark Drilling commented on TEIIDDES-2434: ----------------------------------------- I got the rename issue resolved, but also found an issue with refactor > move. Appears to happen on all OS. Here is the scenario to reproduce: 1) create a project and 3 folders within the project. 'SrcFolder1', 'SrcFolder2', 'ViewFolder'. 2) create a source model within 'SrcFolder1'. 3) create a view model within 'ViewFolder' - transform using the src model you created in SrcFolder1. Should all validate ok. 4) Do Refactor > Move, moving the source model from 'SrcFolder1' to 'SrcFolder2'. 5) After the move, the view model imports did not get updated correctly. Looks like the problem is in RefactorResourcesUtils.calculateImportChanges() or its caller. > Renaming issues - with folders inside project > --------------------------------------------- > > Key: TEIIDDES-2434 > URL: https://issues.jboss.org/browse/TEIIDDES-2434 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 9.0.1 > Environment: Windows > Reporter: Matus Makovy > Assignee: Mark Drilling > Fix For: 9.1, 9.0.2 > > Attachments: renaming-source.png, TestRefactor.zip > > > More issues with renaming models. See steps to reproduce. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2487) Teidd Designer Import SOAP Relational Model Mapping No Columns defined

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2487?page=com.atlassian.jira.plu... ] Ted Jones commented on TEIIDDES-2487: ------------------------------------- This looks like an issue with XSDWildcard handling when we are processing the schema for the response. [~kylin] - Can you please log the enhancements as separate Jira's and add any specific suggestions for improvement you might have? Thanks > Teidd Designer Import SOAP Relational Model Mapping No Columns defined > ---------------------------------------------------------------------- > > Key: TEIIDDES-2487 > URL: https://issues.jboss.org/browse/TEIIDDES-2487 > Project: Teiid Designer > Issue Type: Enhancement > Components: Import/Export > Affects Versions: 9.0 > Reporter: Kylin Soong > Fix For: 9.0.1, 9.0.2 Beta1, 9.0.2 > > Attachments: StateService.jar, teiid-designer-ws-1.png, teiid-designer-ws-2.png, teiid-designer-ws-3.png, teiid-designer-ws-4.png > > > issue > ==== > Create Relational Model from SOAP service validation failed with "No Columns defined error" > Reproduce > ======== > 1. deploy attached StateService to JBoss DV 6.1(assume it DV run on localhost), WSDL File can be viewed via [2] > 2. Use attached 4 pics to import SOAP Web Service will reproduce the issue(teiid-designer-ws-3.png and teiid-designer-ws-4.png show validation errors) > Enhancement > ========== > 1. Simplify the import wizard - from a user's perspective, I think the main obstacle is the wizard is too complex, especially SOAP, federation related wizard, it's very difficult to operate without a step by step documents. > 2. Simplify XML document modeling related operation - current wizard not user-friendly, web should do some enhancement in request/response xml document modeling. > 3. Simplify vdb archive structure - the Designer generated vdb is more complexed compared with dynamic vdb, it have more definition files(sources.xmi, views.xmi, vdb.xml), there also some metamatrix link like [2] exist in .xmi, actually these links not really exist, if we remove these kinds of things, the designer wizard logic may be more easier. > [1] http://localhost:8080/StateService/stateService/StateServiceImpl?WSDL > [2] http://www.metamatrix.com/metamodels/SimpleDatatypes-instance#XMLLiteral -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2487) Teidd Designer Import SOAP Relational Model Mapping No Columns defined

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2487?page=com.atlassian.jira.plu... ] Ted Jones reassigned TEIIDDES-2487: ----------------------------------- Assignee: Ted Jones > Teidd Designer Import SOAP Relational Model Mapping No Columns defined > ---------------------------------------------------------------------- > > Key: TEIIDDES-2487 > URL: https://issues.jboss.org/browse/TEIIDDES-2487 > Project: Teiid Designer > Issue Type: Enhancement > Components: Import/Export > Affects Versions: 9.0 > Reporter: Kylin Soong > Assignee: Ted Jones > Fix For: 9.0.1, 9.0.2 Beta1, 9.0.2 > > Attachments: StateService.jar, teiid-designer-ws-1.png, teiid-designer-ws-2.png, teiid-designer-ws-3.png, teiid-designer-ws-4.png > > > issue > ==== > Create Relational Model from SOAP service validation failed with "No Columns defined error" > Reproduce > ======== > 1. deploy attached StateService to JBoss DV 6.1(assume it DV run on localhost), WSDL File can be viewed via [2] > 2. Use attached 4 pics to import SOAP Web Service will reproduce the issue(teiid-designer-ws-3.png and teiid-designer-ws-4.png show validation errors) > Enhancement > ========== > 1. Simplify the import wizard - from a user's perspective, I think the main obstacle is the wizard is too complex, especially SOAP, federation related wizard, it's very difficult to operate without a step by step documents. > 2. Simplify XML document modeling related operation - current wizard not user-friendly, web should do some enhancement in request/response xml document modeling. > 3. Simplify vdb archive structure - the Designer generated vdb is more complexed compared with dynamic vdb, it have more definition files(sources.xmi, views.xmi, vdb.xml), there also some metamatrix link like [2] exist in .xmi, actually these links not really exist, if we remove these kinds of things, the designer wizard logic may be more easier. > [1] http://localhost:8080/StateService/stateService/StateServiceImpl?WSDL > [2] http://www.metamatrix.com/metamodels/SimpleDatatypes-instance#XMLLiteral -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2487) Teidd Designer Import SOAP Relational Model Mapping No Columns defined

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2487?page=com.atlassian.jira.plu... ] Ted Jones updated TEIIDDES-2487: -------------------------------- Fix Version/s: 9.0.1 9.0.2 Beta1 9.0.2 > Teidd Designer Import SOAP Relational Model Mapping No Columns defined > ---------------------------------------------------------------------- > > Key: TEIIDDES-2487 > URL: https://issues.jboss.org/browse/TEIIDDES-2487 > Project: Teiid Designer > Issue Type: Enhancement > Components: Import/Export > Affects Versions: 9.0 > Reporter: Kylin Soong > Assignee: Ted Jones > Fix For: 9.0.1, 9.0.2 Beta1, 9.0.2 > > Attachments: StateService.jar, teiid-designer-ws-1.png, teiid-designer-ws-2.png, teiid-designer-ws-3.png, teiid-designer-ws-4.png > > > issue > ==== > Create Relational Model from SOAP service validation failed with "No Columns defined error" > Reproduce > ======== > 1. deploy attached StateService to JBoss DV 6.1(assume it DV run on localhost), WSDL File can be viewed via [2] > 2. Use attached 4 pics to import SOAP Web Service will reproduce the issue(teiid-designer-ws-3.png and teiid-designer-ws-4.png show validation errors) > Enhancement > ========== > 1. Simplify the import wizard - from a user's perspective, I think the main obstacle is the wizard is too complex, especially SOAP, federation related wizard, it's very difficult to operate without a step by step documents. > 2. Simplify XML document modeling related operation - current wizard not user-friendly, web should do some enhancement in request/response xml document modeling. > 3. Simplify vdb archive structure - the Designer generated vdb is more complexed compared with dynamic vdb, it have more definition files(sources.xmi, views.xmi, vdb.xml), there also some metamatrix link like [2] exist in .xmi, actually these links not really exist, if we remove these kinds of things, the designer wizard logic may be more easier. > [1] http://localhost:8080/StateService/stateService/StateServiceImpl?WSDL > [2] http://www.metamatrix.com/metamodels/SimpleDatatypes-instance#XMLLiteral -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2482) Enable DDL Importer to import Teiid DDL CREATE VIEW statements to capture and set SQL expression in view model

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2482?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-2482. ------------------------------------ Resolution: Done committed to master: https://github.com/Teiid-Designer/teiid-designer/commit/48f0c493ac7a042ae... > Enable DDL Importer to import Teiid DDL CREATE VIEW statements to capture and set SQL expression in view model > -------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2482 > URL: https://issues.jboss.org/browse/TEIIDDES-2482 > Project: Teiid Designer > Issue Type: Enhancement > Components: Import/Export, Transformations > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 9.1 > > > Teiid DDL supports CREATE VIEW & CREATE PROCEDURE statements that contain SQL expression. The current DDL Importer does not recognize the SQL expression and will not set that value on a table or procedure when importing to a View model. > Make the changes necessary to discover the SQL expression and apply to a virtual table/procedure if importing to a View model. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 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 April 2015