July 2015 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2530) Generate REST Virtual Procedure should use fully qualified names in the generated procedures

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2530?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-2530. ------------------------------------ Resolution: Done > Generate REST Virtual Procedure should use fully qualified names in the generated procedures > -------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2530 > URL: https://issues.jboss.org/browse/TEIIDDES-2530 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling, Transformations > Affects Versions: 9.0.2 > Reporter: Andrej Šmigala > Assignee: Barry LaFond > Fix For: 9.2, 9.0.3 > > > When generating REST procedure using the new Generate REST Virtual Procedures function, the generated procedure contains simple names of the referenced tables, which causes validation errors when there are tables with the same name in other models. > Designer should use the fully qualified name in the generated procedure. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2530) Generate REST Virtual Procedure should use fully qualified names in the generated procedures

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2530?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2530: ---------------------------------------- commits: * master: https://github.com/Teiid-Designer/teiid-designer/commit/1270263f550d3394d... * 9.0.x: https://github.com/Teiid-Designer/teiid-designer/commit/81a69a202161fd76b... > Generate REST Virtual Procedure should use fully qualified names in the generated procedures > -------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2530 > URL: https://issues.jboss.org/browse/TEIIDDES-2530 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling, Transformations > Affects Versions: 9.0.2 > Reporter: Andrej Šmigala > Assignee: Barry LaFond > Fix For: 9.2, 9.0.3 > > > When generating REST procedure using the new Generate REST Virtual Procedures function, the generated procedure contains simple names of the referenced tables, which causes validation errors when there are tables with the same name in other models. > Designer should use the fully qualified name in the generated procedure. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2552) REST connection profile wizard creates URL with parameters in wrong order

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2552?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2552: ---------------------------------------- commits: * master: https://github.com/Teiid-Designer/teiid-designer/commit/80a14a2d738f3d095... * 9.0.x: https://github.com/Teiid-Designer/teiid-designer/commit/2e5aba74920a8ad45... > REST connection profile wizard creates URL with parameters in wrong order > ------------------------------------------------------------------------- > > Key: TEIIDDES-2552 > URL: https://issues.jboss.org/browse/TEIIDDES-2552 > Project: Teiid Designer > Issue Type: Bug > Components: Web Services Support > Affects Versions: 9.0.2 Beta2 > Reporter: Andrej Šmigala > Assignee: Ted Jones > Priority: Critical > Fix For: 9.2, 9.0.3 > > Attachments: Newconnectionprofile_001.png > > > When defining parameters for REST connection profile, they are added to the URL in the order they are defined. This results in wrong URL in case a Query parameter is defined before a URI parameter. > The URI parameters should always be added to the URL before the Query parameters. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2552) REST connection profile wizard creates URL with parameters in wrong order

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2552?page=com.atlassian.jira.plu... ] Ted Jones updated TEIIDDES-2552: -------------------------------- Git Pull Request: https://github.com/Teiid-Designer/teiid-designer/pull/467 > REST connection profile wizard creates URL with parameters in wrong order > ------------------------------------------------------------------------- > > Key: TEIIDDES-2552 > URL: https://issues.jboss.org/browse/TEIIDDES-2552 > Project: Teiid Designer > Issue Type: Bug > Components: Web Services Support > Affects Versions: 9.0.2 Beta2 > Reporter: Andrej Šmigala > Assignee: Ted Jones > Priority: Critical > Fix For: 9.2, 9.0.3 > > Attachments: Newconnectionprofile_001.png > > > When defining parameters for REST connection profile, they are added to the URL in the order they are defined. This results in wrong URL in case a Query parameter is defined before a URI parameter. > The URI parameters should always be added to the URL before the Query parameters. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2560) Although DV 6.0(Teiid 8.4.1) is selected as teiid instance on JBDS, TD 9.0.1 uses grant-all in vdb.xml

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2560?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2560: ---------------------------------------- We can easily detect server version in the data role and vdb editors to prevent grant-all from showing up either TRUE or FALSE, but we can't prevent JaxB from writing out the grantAll attribute in the DataRoleElement class. > Although DV 6.0(Teiid 8.4.1) is selected as teiid instance on JBDS, TD 9.0.1 uses grant-all in vdb.xml > ------------------------------------------------------------------------------------------------------ > > Key: TEIIDDES-2560 > URL: https://issues.jboss.org/browse/TEIIDDES-2560 > Project: Teiid Designer > Issue Type: Bug > Components: Editors > Affects Versions: 9.0.1 > Environment: JBDS8.1 with TD 9.0.1.Final > Reporter: hisao furuichi > Assignee: Barry LaFond > Fix For: 9.2, 9.0.3 > > > The version of Teiid engine in the selected Teiid instance will be displayed on the VDB editor(window for editing user role). So user expects if DV 6.0(Teiid 8.4.1) is selected as a teiid instance, all of modification to a VDB will be optimized for DV 6.0.(Teiid 8.4.1). However grant-all attribute which should not be used for Teiid 8.4.1 is used. (The issue is reported at TEIIDDES-2353) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2580) Upgrade Modeshape jars to latest 3.8.x version

by Barry LaFond (JIRA)

Barry LaFond created TEIIDDES-2580: -------------------------------------- Summary: Upgrade Modeshape jars to latest 3.8.x version Key: TEIIDDES-2580 URL: https://issues.jboss.org/browse/TEIIDDES-2580 Project: Teiid Designer Issue Type: Task Components: Build Reporter: Barry LaFond Assignee: Dan Florian Fix For: 9.2, 9.0.3 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2480) LDAP importer fails silently when no location is explicitly entered for the new model

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2480?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2480: ----------------------------------- Fix Version/s: 9.0.4 (was: 9.0.3) > LDAP importer fails silently when no location is explicitly entered for the new model > ------------------------------------------------------------------------------------- > > Key: TEIIDDES-2480 > URL: https://issues.jboss.org/browse/TEIIDDES-2480 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 9.0 > Reporter: Marc Shirley > Assignee: Paul Richardson > Fix For: 9.2, 9.0.4 > > > LDAP import fails silently when no location is entered for the "Source Model Definition" section's "Location" field on the first page of the wizard. This occurs even when using the context menu to initiate from a specific project or child object level. The wizard functions as expected until you finish, at which point the model is never generated. No error dialog or failure notification is presented to the user. checking error log shows: > java.lang.NullPointerException > at org.teiid.designer.modelgenerator.ldap.RelationalModelBuilder.createNewModelResource(RelationalModelBuilder.java:65) > at org.teiid.designer.modelgenerator.ldap.RelationalModelBuilder.modelEntries(RelationalModelBuilder.java:109) > at org.teiid.designer.modelgenerator.ldap.ui.wizards.LdapImportWizardManager.createModel(LdapImportWizardManager.java:384) > at org.teiid.designer.modelgenerator.ldap.ui.wizards.LdapImportWizard$1.run(LdapImportWizard.java:158) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2478) LDAP import functionality does not handle large number of search results

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2478?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2478: ----------------------------------- Fix Version/s: 9.0.4 (was: 9.0.3) > LDAP import functionality does not handle large number of search results > ------------------------------------------------------------------------ > > Key: TEIIDDES-2478 > URL: https://issues.jboss.org/browse/TEIIDDES-2478 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 9.0 > Reporter: Marc Shirley > Assignee: Paul Richardson > Fix For: 9.2, 9.0.4 > > > LDAP import mechanism does not include paging for when large result sets are returned by the LDAP server. This can result in the importer not including necessary objects and displaying an error like "LDAP: error code 4 - Sizelimit Exceeded". -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2507) XSDWildcard handling SOAP reponse wrongly

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2507?page=com.atlassian.jira.plu... ] Ted Jones updated TEIIDDES-2507: -------------------------------- Fix Version/s: 9.0.4 (was: 9.2) (was: 9.0.3) > XSDWildcard handling SOAP reponse wrongly > ----------------------------------------- > > Key: TEIIDDES-2507 > URL: https://issues.jboss.org/browse/TEIIDDES-2507 > Project: Teiid Designer > Issue Type: Enhancement > Components: Import/Export > Affects Versions: 9.0 > Reporter: Kylin Soong > Assignee: Ted Jones > Fix For: 9.0.4 > > > As TEIIDDES-2487 L3 comments, this issue be created -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 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.4 (was: 9.2) (was: 9.0.3) > 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.4 > > 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.15#6346)

10 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues July 2015