August 2010 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-581) NPE importing DDL into Relational Model with "Set description of model entities to corresponding DDL statement" option checked

by Barry LaFond (JIRA)

NPE importing DDL into Relational Model with "Set description of model entities to corresponding DDL statement" option checked ------------------------------------------------------------------------------------------------------------------------------ Key: TEIIDDES-581 URL: https://jira.jboss.org/browse/TEIIDDES-581 Project: Teiid Designer Issue Type: Bug Components: Import/Export Reporter: Barry LaFond Assignee: John Verhaeg Priority: Critical Fix For: 7.1 I exported Products relational model into both DB2 and SQL Server DDL files. Tried importing them into relational models and checking the "Set description of model entities to corresponding DDL statement" option. In both cases I got NPE's hitting "Next>" or "Finish". See attacheck DDL and Stacktrace log. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

3
10
0 / 0

[JBoss JIRA] Created: (TEIIDDES-584) Teiid View Should Persist View Option Settings From Session To Session

by Dan Florian (JIRA)

Teiid View Should Persist View Option Settings From Session To Session ---------------------------------------------------------------------- Key: TEIIDDES-584 URL: https://jira.jboss.org/browse/TEIIDDES-584 Project: Teiid Designer Issue Type: Bug Affects Versions: 7.0 Environment: Designer 7.0 Reporter: Dan Florian Fix For: 7.1.1 In the Teiid View users can elect to view or filter out Preview VDBs and Preview data sources by using the view menu. There are also other filtering options. The state of these filtering options should be persisted from session to session. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-520) Designer permits VDB to have no visible models - at least one should be visible

by Paul Nittel (JIRA)

Designer permits VDB to have no visible models - at least one should be visible ------------------------------------------------------------------------------- Key: TEIIDDES-520 URL: https://jira.jboss.org/browse/TEIIDDES-520 Project: Teiid Designer Issue Type: Bug Components: VDB & Execution Affects Versions: 7.0 Environment: Fedora 12, JBDS 3.0.1, Teiid 7 Designer Reporter: Paul Nittel While testing model visibility, I saw I was able to create (and even deploy!) a VDB which had no visible models. There needs to be at least one which is visible. (At the least, the VDB should have an error when deployed.) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

4
7
0 / 0

[JBoss JIRA] Created: (TEIIDDES-508) Change default value of visibility for source (physical) models to FALSE (not visible)

by Paul Nittel (JIRA)

Change default value of visibility for source (physical) models to FALSE (not visible) -------------------------------------------------------------------------------------- Key: TEIIDDES-508 URL: https://jira.jboss.org/browse/TEIIDDES-508 Project: Teiid Designer Issue Type: Task Components: VDB & Execution Affects Versions: 7.0 Environment: All Reporter: Paul Nittel After discussing security concerns (Friday, July 16, 2010), it was decided that physical models should not be visible, by default. The Designer user continues to have the option to make them visible. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
6
0 / 0

[JBoss JIRA] Created: (TEIIDDES-577) Models which are NOT visible should not be shown in the data roles editor

by Paul Nittel (JIRA)

Models which are NOT visible should not be shown in the data roles editor ------------------------------------------------------------------------- Key: TEIIDDES-577 URL: https://jira.jboss.org/browse/TEIIDDES-577 Project: Teiid Designer Issue Type: Bug Components: VDB & Execution Affects Versions: 7.1 Environment: All Reporter: Paul Nittel Attachments: visible.png At the risk of opening huge cans of worms, a model which has been marked NOT VISIBLE should not be shown in the data roles editor. Presently, they are shown in that editor. They should not be. Screenshot is attached. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

4
7
0 / 0

[JBoss JIRA] Created: (TEIIDDES-588) The "Create Data Source" dialog only displays JDBC profiles.

by John Doyle (JIRA)

The "Create Data Source" dialog only displays JDBC profiles. ------------------------------------------------------------ Key: TEIIDDES-588 URL: https://jira.jboss.org/browse/TEIIDDES-588 Project: Teiid Designer Issue Type: Bug Components: Dialogs Affects Versions: 7.1 Reporter: John Doyle Assignee: John Doyle Fix For: 7.1.1 The "Create Data Source" dialog that is displayed when you select Modeling->Create Teiid Data Source displays a list of Connection Profiles to choose from. The list is only displaying JDBC profiles, so there's no way to select a SalesForce, SOAP, or LDAP profile. Two fixes come to mind. 1. Add a filter dropdown above the existing Connection Profile dropdown that allows a user to select the type of profile to display in the list. 2. Create a larger list by fetching all of the Profiles of Type JDBC and type Teiid Importer. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-476) JDBC Importer no longer provides ability to edit connection information

by John Verhaeg (JIRA)

JDBC Importer no longer provides ability to edit connection information ----------------------------------------------------------------------- Key: TEIIDDES-476 URL: https://jira.jboss.org/browse/TEIIDDES-476 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 7.0 Reporter: John Verhaeg Fix For: 7.0 After creating a connection profile via the JDBC importer dialog, I could no longer go back and edit its values (such as password). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
5
0 / 0

[JBoss JIRA] Created: (TEIIDDES-533) Implement DS creation for LDAP.

by John Doyle (JIRA)

Implement DS creation for LDAP. ------------------------------- Key: TEIIDDES-533 URL: https://jira.jboss.org/browse/TEIIDDES-533 Project: Teiid Designer Issue Type: Feature Request Affects Versions: 7.1 Reporter: John Doyle Assignee: John Doyle Fix For: 7.1 We need to retain the ability to create LDAP connections in Teiid from Designer. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-580) Selecting DDL file from "Workspace" results in wizard error "Provide a valid path to the DDL file to import. The supplied DDL file does not exist."

by Barry LaFond (JIRA)

Selecting DDL file from "Workspace" results in wizard error "Provide a valid path to the DDL file to import. The supplied DDL file does not exist." --------------------------------------------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-580 URL: https://jira.jboss.org/browse/TEIIDDES-580 Project: Teiid Designer Issue Type: Bug Components: Import/Export Reporter: Barry LaFond Assignee: John Verhaeg Priority: Critical Fix For: 7.1 Selecting a DDL file in my Designer's workspace results in wizard error and can't FINISH "Provide a valid path to the DDL file to import. The supplied DDL file does not exist." To set up, I "Exported" a model file into DDL into my workspace directory on file system, turned on "Show All File Types", then refreshed Model Explorer to verify ddl file. Then tried to Import > DDL into Relational Model. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-264) Reimplement binding creation for the Salesforce importer around new admin API.

by John Doyle (JIRA)

Reimplement binding creation for the Salesforce importer around new admin API. ------------------------------------------------------------------------------ Key: TEIIDDES-264 URL: https://jira.jboss.org/jira/browse/TEIIDDES-264 Project: Teiid Designer Issue Type: Task Components: Import/Export Affects Versions: 7.0 Reporter: John Doyle Assignee: John Doyle Fix For: 7.0 The api for creating connector bindings is changing. The old code is now commented out and will have to be replaced when the new API is integrated. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues August 2010