June 2010 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-456) Create ConnectionProfiles from deployed VDBs

by John Doyle (JIRA)

Create ConnectionProfiles from deployed VDBs -------------------------------------------- Key: TEIIDDES-456 URL: https://jira.jboss.org/browse/TEIIDDES-456 Project: Teiid Designer Issue Type: Sub-task Affects Versions: 7.0 Reporter: John Doyle Assignee: John Doyle Fix For: 7.0 Assume that a VDB is deployed and running in Teiid. In order to test the VDB in the DTP views a ConectionProfile must be created. This can already be done by the user manually, but in the case where a user is deploying from Designer we want the ability to create a ConnectionProfile for the user. This is an intermediate step before invoking the Database Development perspective for query testing. -- 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

15 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-449) Data tools plug-ins have lots of warnings that need to be addressed

by John Verhaeg (JIRA)

Data tools plug-ins have lots of warnings that need to be addressed ------------------------------------------------------------------- Key: TEIIDDES-449 URL: https://jira.jboss.org/browse/TEIIDDES-449 Project: Teiid Designer Issue Type: Task Affects Versions: 7.0 Reporter: John Verhaeg I cleaned up some of the warnings, but there are 3 types left that John Doyle needs to address: 1) The most prevalent warnings are about strings that haven't been externalized in the code, the plugin.xml, and the MANIFEST.MF. All of these need to be internationalized or, if not applicable, marked with NLS tags 2) A couple of the attributes specified in the plugin.xml have been deprecated. 3) There are 2 warnings about API baselines not being set on the project. Not sure how or why the API tooling nature got set on these projects, but I removed the nature and builders from the .projects files, along with the .externalBuilder... folders, but still see the warnings for some reason. -- 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

15 years, 9 months

2
8
0 / 0

[JBoss JIRA] Created: (TEIIDDES-426) Chang the WSDL to Relational Importer's XSD resolution mechanism to the Web Tools impl

by John Doyle (JIRA)

Chang the WSDL to Relational Importer's XSD resolution mechanism to the Web Tools impl -------------------------------------------------------------------------------------- Key: TEIIDDES-426 URL: https://jira.jboss.org/jira/browse/TEIIDDES-426 Project: Teiid Designer Issue Type: Task Components: Import/Export Reporter: John Doyle Assignee: John Doyle Fix For: 7.0 Before we had Web Tools in designer the WSDL to Relatinal importer had to resolve unknown XSDs and WSDLs on it's own. Web Tools has a mechanism for this and we should remove out workaround and use the standard mechanism. See JBEDSP_1007 -- 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

15 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-236) Salesforce connector does not bind the connector binding to the model.

by John Doyle (JIRA)

Salesforce connector does not bind the connector binding to the model. ---------------------------------------------------------------------- Key: TEIIDDES-236 URL: https://jira.jboss.org/jira/browse/TEIIDDES-236 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 6.1.0, 6.2.0 Reporter: John Doyle Assignee: John Doyle Fix For: 6.3 -- 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

15 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-233) Treat Teiid VDB as source in DTP. Utilize DTP project views and capabilities to perform data preview through VDB's.

by Barry LaFond (JIRA)

Treat Teiid VDB as source in DTP. Utilize DTP project views and capabilities to perform data preview through VDB's. ------------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-233 URL: https://jira.jboss.org/jira/browse/TEIIDDES-233 Project: Teiid Designer Issue Type: Feature Request Components: VDB & Execution Reporter: Barry LaFond Fix For: 6.4 Replacing the SQL Explorer and associated code will simplify Teiid Designer. This can only be done by replacing that functionality. The Data Tools Platform provides data-source/connection capability which is mostly compatible with Teiid Designer. This feature would treat Teiid (and VDB's) as just another data source. Work would have to be done to discover VDB's deployed on a server. -- 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

15 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-254) Salesforce Importer allows a user to proceed even if the credentials are invalid.

by John Doyle (JIRA)

Salesforce Importer allows a user to proceed even if the credentials are invalid. ---------------------------------------------------------------------------------- Key: TEIIDDES-254 URL: https://jira.jboss.org/jira/browse/TEIIDDES-254 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 6.2.0, 6.1.0, 6.0.0, 6.3 Reporter: John Doyle Assignee: John Doyle See the linked ticket. -- 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

15 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-241) SalesForce Importer fails to import if Extensions model is not in an open project

by John Doyle (JIRA)

SalesForce Importer fails to import if Extensions model is not in an open project --------------------------------------------------------------------------------- Key: TEIIDDES-241 URL: https://jira.jboss.org/jira/browse/TEIIDDES-241 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 6.1.0, 6.2.0 Reporter: John Doyle Assignee: John Doyle Fix For: Future -- 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

15 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-446) Connection Profile MRU for JDBC Import is not updated when Connection Profile Name is changed in DTP perspective. Results in exception.

by Barry LaFond (JIRA)

Connection Profile MRU for JDBC Import is not updated when Connection Profile Name is changed in DTP perspective. Results in exception. --------------------------------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-446 URL: https://jira.jboss.org/browse/TEIIDDES-446 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 7.0 Reporter: Barry LaFond Assignee: John Doyle Priority: Critical Fix For: 7.0 Playing with new DTP driven JDBC Importer. 1) Launched JDBC Import wizard and created SQL Server connection profile to books and took default name "New SQL Server" 2) Model New_SQL_Server was created. 3) Opend DTP perspective and performed a "Rename" action to changed "New SQL Server" to "BooksSQL" 4) launched JDBC Import again and the MRU list did not reflect the new name. 5) Selecting "Next" button resulted in exception: !ENTRY org.teiid.designer.jdbc.ui 4 0 2010-05-24 10:30:42.332 !MESSAGE ConnectionProfile New SQL Server cannot be found !STACK 1 Modeler Core Exception: Status ERROR: org.teiid.core.designer code=0 ConnectionProfile New SQL Server cannot be found null at com.metamatrix.modeler.internal.jdbc.JdbcManagerImpl.createConnection(JdbcManagerImpl.java:290) at com.metamatrix.modeler.internal.jdbc.JdbcManagerImpl.createConnection(JdbcManagerImpl.java:282) at com.metamatrix.modeler.internal.jdbc.ui.util.JdbcUiUtil$1.run(JdbcUiUtil.java:84) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) !SUBENTRY 1 org.teiid.core.designer 4 0 2010-05-24 10:30:42.334 !MESSAGE ConnectionProfile New SQL Server cannot be found -- 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

15 years, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-129) WSDL to Relational Importer models only one service from a WSDL defining multiple services.

by John Doyle (JIRA)

WSDL to Relational Importer models only one service from a WSDL defining multiple services. ------------------------------------------------------------------------------------------- Key: TEIIDDES-129 URL: https://jira.jboss.org/jira/browse/TEIIDDES-129 Project: Teiid Designer Issue Type: Bug Components: Import/Export Reporter: John Doyle Assignee: John Doyle Attachments: pricelist_twoServices.wsdl The attached WSDL defined two services. When importing from this WSDL, the importer UI correctly displays the metadata of the two services, but only the model for one is generated by the importer. We need to generate multiple models and bindings for this case. -- 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

15 years, 9 months

2
7
0 / 0

[JBoss JIRA] Created: (TEIIDDES-234) WSDL Relational Importer creates tables that could be collapsed out of the model.

by John Doyle (JIRA)

WSDL Relational Importer creates tables that could be collapsed out of the model. --------------------------------------------------------------------------------- Key: TEIIDDES-234 URL: https://jira.jboss.org/jira/browse/TEIIDDES-234 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 6.0.0 Reporter: John Doyle Assignee: John Doyle Priority: Minor Fix For: Future The attached WSDL and XSD's create a model with a Request Table, Response Table, an intermediate table that has only mmid's, and finally a table (Order) containing all of the data. (it is invalid because of JBEDSP-514, but that's not material). While this model valid and will work once the table name conflict from 514 is addressed, it's not optimal. The intermediate table is not required in the model because there is no multiplicity above the Order table. The intermediate table can be removed and the Order table linked directly to the response and the simplicity of the model will be improved with no loss of capability. The importer could be enhanced to recognize this possibility. -- 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

15 years, 9 months

1
3
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues June 2010