May 2010 - teiid-designer-issues - Jboss List Archives

[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, 4 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, 4 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, 4 months

1
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-418) Salesforce Import wizard fails and has to be restarted if invalid credentials are entered.

by Debbie Steigner (JIRA)

Salesforce Import wizard fails and has to be restarted if invalid credentials are entered. ------------------------------------------------------------------------------------------ Key: TEIIDDES-418 URL: https://jira.jboss.org/jira/browse/TEIIDDES-418 Project: Teiid Designer Issue Type: Bug Components: Import/Export Reporter: Debbie Steigner Fix For: 7.0 In the Import Salesforce login window during import, if i enter incorrect username or password, click validate credentials which will throw an error message of incorrect username or password. Then, enter correct username/password but clicking validate credentials does not do anything. So you have to close the wizard and run it again. -- 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, 4 months

3
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-445) Change JDBC Importer to use DTP maintainted ConnectionProfiles

by John Doyle (JIRA)

Change JDBC Importer to use DTP maintainted ConnectionProfiles -------------------------------------------------------------- Key: TEIIDDES-445 URL: https://jira.jboss.org/browse/TEIIDDES-445 Project: Teiid Designer Issue Type: Sub-task Components: Import/Export Affects Versions: 7.0 Reporter: John Doyle Assignee: John Doyle Priority: Blocker Fix For: 7.0 As part of the DTP integration, we are no longer maintaining JDBC metadata in our own code, we're using DTP ConnectionProifles. The JDBC importer needs to become aware of the DTP CP's -- 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, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-208) Salesforce Importer throws javax.net.ssl.SSLException when validating credentials.

by John Doyle (JIRA)

Salesforce Importer throws javax.net.ssl.SSLException when validating credentials. ---------------------------------------------------------------------------------- Key: TEIIDDES-208 URL: https://jira.jboss.org/jira/browse/TEIIDDES-208 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 6.1.0 Reporter: John Doyle Assignee: John Doyle Fix For: Future Salesforce Importer throws javax.net.ssl.SSLException when validating credentials. The full text of the message is: javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLException: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty This occurs because the cacerts file is not found. -- 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, 4 months

1
6
0 / 0

[JBoss JIRA] Created: (TEIIDDES-232) Remove SQL Explorer

by Barry LaFond (JIRA)

Remove SQL Explorer ------------------- Key: TEIIDDES-232 URL: https://jira.jboss.org/jira/browse/TEIIDDES-232 Project: Teiid Designer Issue Type: Task Components: VDB & Execution Affects Versions: 6.4 Reporter: Barry LaFond Fix For: 6.4 -- 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, 5 months

1
6
0 / 0

[JBoss JIRA] Created: (TEIIDDES-411) Remove VDB Execution Tab in VDB Editor. Add connector selection and name field functionality to VDB Editor Model Summary page.

by Barry LaFond (JIRA)

Remove VDB Execution Tab in VDB Editor. Add connector selection and name field functionality to VDB Editor Model Summary page. ------------------------------------------------------------------------------------------------------------------------------ Key: TEIIDDES-411 URL: https://jira.jboss.org/jira/browse/TEIIDDES-411 Project: Teiid Designer Issue Type: Sub-task Components: VDB & Execution Affects Versions: 7.0 Reporter: Barry LaFond Priority: Blocker Fix For: 7.0 The VDB Execution tab is redundant and needs to be removed and somewhat replaced with simpler functionality. 1) Remove ConnectorBindingsEditPart 2) Remove all associated Connector creation/editing dialogs and panels 3) Add Field for each model in VDB Model Summary Panel for Connector Name 4) Add combo Box to same page to select 1 teiid server (or none) 5) Add combo box selector to each model row to select/change connector 6) Add validation as required. 7) Allow connector name to be a text field that can be overridden by user. Should just be a name. -- 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, 5 months

3
7
0 / 0

[JBoss JIRA] Created: (TEIIDDES-407) Replace Designer's workspace source binding management framework with Server-managed framework

by Barry LaFond (JIRA)

Replace Designer's workspace source binding management framework with Server-managed framework ---------------------------------------------------------------------------------------------- Key: TEIIDDES-407 URL: https://jira.jboss.org/jira/browse/TEIIDDES-407 Project: Teiid Designer Issue Type: Sub-task Components: Teiid Integration, VDB & Execution Affects Versions: 7.0 Reporter: Barry LaFond Fix For: 7.0 Source bindings were managed in 6.3 Designer. The Teiid API provides assignBindingToModel() method for VDB's deployed to Teiid. By creating a "hidden" VDB for each running Server, we can manager these source bindings via that hidden VDB. This will required Creating the hidden VDB, managing it's life cycle, providing utility methods to assign/remove source bindings based on model edits (Delete/Rename) etc.. -- 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, 5 months

1
5
0 / 0

[JBoss JIRA] Created: (TEIIDDES-412) Expose Bound Workspace models in Execution View for each Teiid Server

by Barry LaFond (JIRA)

Expose Bound Workspace models in Execution View for each Teiid Server --------------------------------------------------------------------- Key: TEIIDDES-412 URL: https://jira.jboss.org/jira/browse/TEIIDDES-412 Project: Teiid Designer Issue Type: Sub-task Components: VDB & Execution Affects Versions: 7.0 Reporter: Barry LaFond Fix For: 7.0 To assist the user in both creating/changing and viewing workspace source-to-connector bindings, show a "workspace models" root under each Teiid Server root showing each bound model and it's current connector binding. The reverse of this is to maintain a "connector-to-source" binding object in the Model Explorer view for each source model. (if bound) -- 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, 5 months

1
4
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues May 2010