March 2015 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2455) Changing Fields in SOAP Importer Schema Element Editor Causes Designer to Hang

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2455?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2455: ----------------------------------- Fix Version/s: 9.1 9.0.2 > Changing Fields in SOAP Importer Schema Element Editor Causes Designer to Hang > ------------------------------------------------------------------------------ > > Key: TEIIDDES-2455 > URL: https://issues.jboss.org/browse/TEIIDDES-2455 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Affects Versions: 8.3.4 > Reporter: Ted Jones > Assignee: Ted Jones > Fix For: 9.1, 9.0.2 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2452) The result of wsdl validation in SOAP web-service importer is not shown for a user

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2452?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2452: ----------------------------------- Fix Version/s: 9.2 > The result of wsdl validation in SOAP web-service importer is not shown for a user > ---------------------------------------------------------------------------------- > > Key: TEIIDDES-2452 > URL: https://issues.jboss.org/browse/TEIIDDES-2452 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.6.1 > Environment: JBDS 7.1.1 > JBDSIS 7.1.0 > Windows 7 > Reporter: Filip Elias > Priority: Minor > Fix For: 9.2 > > > Steps to reproduce: > 1, File> Import > Web Service Source >> Source and View Mode (SOAP) > 2, Select connection profile > 3, Click Validate WSDL > If the wsdl or URL is incorrect the TD will display error. > However if the wsdl or URL is OK then the TD won't display any message about successful validation and the button became greyish. > User should be informed that the validation finished successfully. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2456) Teiid Connection Importer: IllegalArgumentException after obtaining the DDL from server

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2456?page=com.atlassian.jira.plu... ] Barry LaFond reassigned TEIIDDES-2456: -------------------------------------- Assignee: Mark Drilling > Teiid Connection Importer: IllegalArgumentException after obtaining the DDL from server > --------------------------------------------------------------------------------------- > > Key: TEIIDDES-2456 > URL: https://issues.jboss.org/browse/TEIIDDES-2456 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export, Teiid Integration > Affects Versions: 9.0.1 > Reporter: Andrej Šmigala > Assignee: Mark Drilling > Fix For: 9.1, 9.0.2 > > Attachments: screenshot.png > > > Import using Teiid Connection sometimes fails with the following error message after getting the DDL from server and clicking Next: > {code} > Error encountered while importing the DDL: "java.lang.IllegalArgumentException: Expected argument to be non-null but got null" > {code} > Stacktrace: > {code} > !ENTRY org.teiid.designer.ddl.importer.ui 4 0 2015-03-23 14:58:16.966 > !MESSAGE Error encountered while importing the DDL: "java.lang.IllegalArgumentException: Expected argument to be non-null but got null" > !STACK 0 > java.lang.Exception: java.lang.IllegalArgumentException: Expected argument to be non-null but got null > at org.teiid.core.designer.util.OperationUtil.perform(OperationUtil.java:54) > at org.teiid.designer.ddl.importer.DdlImporter.importDdl(DdlImporter.java:101) > at org.teiid.designer.ddl.importer.ui.DdlImportDifferencesPage$1.run(DdlImportDifferencesPage.java:225) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122) > Caused by: java.lang.IllegalArgumentException: Expected argument to be non-null but got null > at org.teiid.core.designer.util.CoreArgCheck.isNotNull(CoreArgCheck.java:142) > at org.teiid.core.designer.util.CoreArgCheck.isNotNull(CoreArgCheck.java:128) > at org.teiid.designer.core.ModelEditorImpl.getModelName(ModelEditorImpl.java:4971) > at org.teiid.designer.relational.model.RelationalReferenceFactory.createRelationalModel(RelationalReferenceFactory.java:65) > at org.teiid.designer.ddl.importer.DdlImporter.importDdl(DdlImporter.java:188) > at org.teiid.designer.ddl.importer.DdlImporter$1.tryToDo(DdlImporter.java:117) > at org.teiid.core.designer.util.OperationUtil.perform(OperationUtil.java:41) > ... 3 more > {code} > (02:50:28 PM) blafond: I'll need a stack trace to figure it out > (02:50:35 PM) blafond: check Designer's Error Log view? > (02:50:39 PM) asmigala: the weird thing is, it sometimes works for the same data source > (02:50:42 PM) asmigala: ok, hang on a sec > (02:50:53 PM) asmigala: so this is not something we know about? > (02:51:34 PM) blafond: not as a reproduceable bug. > ... > (02:59:47 PM) asmigala: also, when I copy the DDL, save it to a file and then use the DDL importer, it works correctlu > 03:05:15 PM) blafond: I think it's a threading/timing issue. The RelationalReferenceFactory is assuming that the new EMF Model already created. Looks like it's still in the process "sometimes" and ends up failing. > (03:05:45 PM) blafond: I noticed that we don't save the model right after we create it. Maybe that could fix the issue. > (03:06:05 PM) blafond: Please log a JIRA/BZ and include all of this conversation > (03:06:59 PM) asmigala: yes, that makes sense, I generally don't see it when stepping through the test -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2455) Changing Fields in SOAP Importer Schema Element Editor Causes Designer to Hang

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2455?page=com.atlassian.jira.plu... ] Barry LaFond reassigned TEIIDDES-2455: -------------------------------------- Assignee: Ted Jones > Changing Fields in SOAP Importer Schema Element Editor Causes Designer to Hang > ------------------------------------------------------------------------------ > > Key: TEIIDDES-2455 > URL: https://issues.jboss.org/browse/TEIIDDES-2455 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Affects Versions: 8.3.4 > Reporter: Ted Jones > Assignee: Ted Jones > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2456) Teiid Connection Importer: IllegalArgumentException after obtaining the DDL from server

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2456?page=com.atlassian.jira.plu... ] Barry LaFond reassigned TEIIDDES-2456: -------------------------------------- Assignee: Barry LaFond (was: Mark Drilling) > Teiid Connection Importer: IllegalArgumentException after obtaining the DDL from server > --------------------------------------------------------------------------------------- > > Key: TEIIDDES-2456 > URL: https://issues.jboss.org/browse/TEIIDDES-2456 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export, Teiid Integration > Affects Versions: 9.0.1 > Reporter: Andrej Šmigala > Assignee: Barry LaFond > Fix For: 9.1, 9.0.2 > > Attachments: screenshot.png > > > Import using Teiid Connection sometimes fails with the following error message after getting the DDL from server and clicking Next: > {code} > Error encountered while importing the DDL: "java.lang.IllegalArgumentException: Expected argument to be non-null but got null" > {code} > Stacktrace: > {code} > !ENTRY org.teiid.designer.ddl.importer.ui 4 0 2015-03-23 14:58:16.966 > !MESSAGE Error encountered while importing the DDL: "java.lang.IllegalArgumentException: Expected argument to be non-null but got null" > !STACK 0 > java.lang.Exception: java.lang.IllegalArgumentException: Expected argument to be non-null but got null > at org.teiid.core.designer.util.OperationUtil.perform(OperationUtil.java:54) > at org.teiid.designer.ddl.importer.DdlImporter.importDdl(DdlImporter.java:101) > at org.teiid.designer.ddl.importer.ui.DdlImportDifferencesPage$1.run(DdlImportDifferencesPage.java:225) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122) > Caused by: java.lang.IllegalArgumentException: Expected argument to be non-null but got null > at org.teiid.core.designer.util.CoreArgCheck.isNotNull(CoreArgCheck.java:142) > at org.teiid.core.designer.util.CoreArgCheck.isNotNull(CoreArgCheck.java:128) > at org.teiid.designer.core.ModelEditorImpl.getModelName(ModelEditorImpl.java:4971) > at org.teiid.designer.relational.model.RelationalReferenceFactory.createRelationalModel(RelationalReferenceFactory.java:65) > at org.teiid.designer.ddl.importer.DdlImporter.importDdl(DdlImporter.java:188) > at org.teiid.designer.ddl.importer.DdlImporter$1.tryToDo(DdlImporter.java:117) > at org.teiid.core.designer.util.OperationUtil.perform(OperationUtil.java:41) > ... 3 more > {code} > (02:50:28 PM) blafond: I'll need a stack trace to figure it out > (02:50:35 PM) blafond: check Designer's Error Log view? > (02:50:39 PM) asmigala: the weird thing is, it sometimes works for the same data source > (02:50:42 PM) asmigala: ok, hang on a sec > (02:50:53 PM) asmigala: so this is not something we know about? > (02:51:34 PM) blafond: not as a reproduceable bug. > ... > (02:59:47 PM) asmigala: also, when I copy the DDL, save it to a file and then use the DDL importer, it works correctlu > 03:05:15 PM) blafond: I think it's a threading/timing issue. The RelationalReferenceFactory is assuming that the new EMF Model already created. Looks like it's still in the process "sometimes" and ends up failing. > (03:05:45 PM) blafond: I noticed that we don't save the model right after we create it. Maybe that could fix the issue. > (03:06:05 PM) blafond: Please log a JIRA/BZ and include all of this conversation > (03:06:59 PM) asmigala: yes, that makes sense, I generally don't see it when stepping through the test -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2456) Teiid Connection Importer: IllegalArgumentException after obtaining the DDL from server

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2456?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2456: ----------------------------------- Fix Version/s: 9.1 9.0.2 > Teiid Connection Importer: IllegalArgumentException after obtaining the DDL from server > --------------------------------------------------------------------------------------- > > Key: TEIIDDES-2456 > URL: https://issues.jboss.org/browse/TEIIDDES-2456 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export, Teiid Integration > Affects Versions: 9.0.1 > Reporter: Andrej Šmigala > Assignee: Mark Drilling > Fix For: 9.1, 9.0.2 > > Attachments: screenshot.png > > > Import using Teiid Connection sometimes fails with the following error message after getting the DDL from server and clicking Next: > {code} > Error encountered while importing the DDL: "java.lang.IllegalArgumentException: Expected argument to be non-null but got null" > {code} > Stacktrace: > {code} > !ENTRY org.teiid.designer.ddl.importer.ui 4 0 2015-03-23 14:58:16.966 > !MESSAGE Error encountered while importing the DDL: "java.lang.IllegalArgumentException: Expected argument to be non-null but got null" > !STACK 0 > java.lang.Exception: java.lang.IllegalArgumentException: Expected argument to be non-null but got null > at org.teiid.core.designer.util.OperationUtil.perform(OperationUtil.java:54) > at org.teiid.designer.ddl.importer.DdlImporter.importDdl(DdlImporter.java:101) > at org.teiid.designer.ddl.importer.ui.DdlImportDifferencesPage$1.run(DdlImportDifferencesPage.java:225) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122) > Caused by: java.lang.IllegalArgumentException: Expected argument to be non-null but got null > at org.teiid.core.designer.util.CoreArgCheck.isNotNull(CoreArgCheck.java:142) > at org.teiid.core.designer.util.CoreArgCheck.isNotNull(CoreArgCheck.java:128) > at org.teiid.designer.core.ModelEditorImpl.getModelName(ModelEditorImpl.java:4971) > at org.teiid.designer.relational.model.RelationalReferenceFactory.createRelationalModel(RelationalReferenceFactory.java:65) > at org.teiid.designer.ddl.importer.DdlImporter.importDdl(DdlImporter.java:188) > at org.teiid.designer.ddl.importer.DdlImporter$1.tryToDo(DdlImporter.java:117) > at org.teiid.core.designer.util.OperationUtil.perform(OperationUtil.java:41) > ... 3 more > {code} > (02:50:28 PM) blafond: I'll need a stack trace to figure it out > (02:50:35 PM) blafond: check Designer's Error Log view? > (02:50:39 PM) asmigala: the weird thing is, it sometimes works for the same data source > (02:50:42 PM) asmigala: ok, hang on a sec > (02:50:53 PM) asmigala: so this is not something we know about? > (02:51:34 PM) blafond: not as a reproduceable bug. > ... > (02:59:47 PM) asmigala: also, when I copy the DDL, save it to a file and then use the DDL importer, it works correctlu > 03:05:15 PM) blafond: I think it's a threading/timing issue. The RelationalReferenceFactory is assuming that the new EMF Model already created. Looks like it's still in the process "sometimes" and ends up failing. > (03:05:45 PM) blafond: I noticed that we don't save the model right after we create it. Maybe that could fix the issue. > (03:06:05 PM) blafond: Please log a JIRA/BZ and include all of this conversation > (03:06:59 PM) asmigala: yes, that makes sense, I generally don't see it when stepping through the test -- 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.1 > 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-2388) Add SAP HANA Driver Type

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2388?page=com.atlassian.jira.plu... ] Barry LaFond reassigned TEIIDDES-2388: -------------------------------------- Assignee: Ted Jones > Add SAP HANA Driver Type > ------------------------ > > Key: TEIIDDES-2388 > URL: https://issues.jboss.org/browse/TEIIDDES-2388 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling > Affects Versions: 8.6.1 > Reporter: Ted Jones > Assignee: Ted Jones > Fix For: 9.1 > > > Need to add the SAP HANA driver to our list of drivers. The URL should be "jdbc:sap://{host:port}" -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2398) Inconsistent column datatypes when importing

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2398?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2398: ---------------------------------------- Check what the Teiid DDL datatypes are coming in as vs JDBC data types. Teiid DDL could be pulling d-types from the source and tweaking them. It may or not be a Designer issue or may be a combination. > Inconsistent column datatypes when importing > -------------------------------------------- > > Key: TEIIDDES-2398 > URL: https://issues.jboss.org/browse/TEIIDDES-2398 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export, Modeling > Reporter: Andrej Šmigala > Assignee: Mark Drilling > Fix For: 9.1, 9.0.2, 8.6.2 > > Attachments: datatypes.png > > > There are multiple discrepancies in the column datatypes when importing using JDBC importer vs when using Teiid Connection importer. > Also some of the imported datatypes seem completely wrong (e.g. bigdecimal for almost all numeric datatypes in oracle) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2398) Inconsistent column datatypes when importing

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2398?page=com.atlassian.jira.plu... ] Barry LaFond reassigned TEIIDDES-2398: -------------------------------------- Assignee: Mark Drilling > Inconsistent column datatypes when importing > -------------------------------------------- > > Key: TEIIDDES-2398 > URL: https://issues.jboss.org/browse/TEIIDDES-2398 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export, Modeling > Reporter: Andrej Šmigala > Assignee: Mark Drilling > Fix For: 9.1, 9.0.2, 8.6.2 > > Attachments: datatypes.png > > > There are multiple discrepancies in the column datatypes when importing using JDBC importer vs when using Teiid Connection importer. > Also some of the imported datatypes seem completely wrong (e.g. bigdecimal for almost all numeric datatypes in oracle) -- 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