October 2010 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-189) Plugin details shows version, but not build number

by Paul Nittel (JIRA)

Plugin details shows version, but not build number -------------------------------------------------- Key: TEIIDDES-189 URL: https://jira.jboss.org/jira/browse/TEIIDDES-189 Project: Teiid Designer Issue Type: Bug Components: Build Affects Versions: 6.0.0 Environment: Fedora 10 Reporter: Paul Nittel Since the plugin details shows only the version (6.0.0), there is no way to determine from which build this came. We really need this ability back. -- 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

14 years, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-689) Needs to be some indication to user that a data source needs to be created

by John Verhaeg (JIRA)

Needs to be some indication to user that a data source needs to be created -------------------------------------------------------------------------- Key: TEIIDDES-689 URL: https://jira.jboss.org/browse/TEIIDDES-689 Project: Teiid Designer Issue Type: Feature Request Components: Teiid Integration Affects Versions: 7.1 Reporter: John Verhaeg After creating one or more models and putting them in a VDB, there is no indication that the user needs to have a corresponding data source available on the server before they can successfully deploy that VDB. -- 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

14 years, 5 months

3
9
0 / 0

[JBoss JIRA] Created: (TEIIDDES-171) VDB Editor allows adding multiple Salesforce generated relational models.

by Barry LaFond (JIRA)

VDB Editor allows adding multiple Salesforce generated relational models. ------------------------------------------------------------------------- Key: TEIIDDES-171 URL: https://jira.jboss.org/jira/browse/TEIIDDES-171 Project: Teiid Designer Issue Type: Bug Components: VDB & Execution Affects Versions: 6.0.0 Reporter: Barry LaFond Fix For: 6.1.0 While investigating TEIIDDES-168, I tried to add a second Salesforce model to a VDB. I had already added "sf.xmi" which auto-added the XMLSOAPConnectorExtensions.xmi model. But adding "stock.xmi", which depends on a DIFFERENT XMLSOAPConnectorExtensions.xmi file, it added "stock.xmi" thinking it already had the right XMLSOAPConnectorExtensions.xmi file. So, there is a bug here where VDB Editor should have detected the actual dependent XMLSOAPConnectorExtensions.xmi file and NOT allowed adding stock.xmi -- 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

14 years, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-126) Add a warning for the use of a model supports property

by Steven Hawkins (JIRA)

Add a warning for the use of a model supports property ------------------------------------------------------ Key: TEIIDDES-126 URL: https://jira.jboss.org/jira/browse/TEIIDDES-126 Project: Teiid Designer Issue Type: Quality Risk Components: Modeling Affects Versions: 6.0.0 Reporter: Steven Hawkins See TEIID-131. Model support properties that are simply overrides for connector binding properties are no longer checked by the Teiid runtime, rather TEIID-205 is used to control specific capabilities through the connector binding without requiring the creation of a custom capabilities class. Usage of 'Set Criteria Max Size', Supports "Distinct', Supports "Join", Supports "Order By", Supports "Outer Join", and Supports "Where all" should generate a warning stating that the connector binding should be used instead. -- 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

14 years, 5 months

2
6
0 / 0

[JBoss JIRA] Created: (TEIIDDES-417) Metadata from Text File importer requires use of file Browse button even though file can be entered manually - Finish button is enabled

by Paul Nittel (JIRA)

Metadata from Text File importer requires use of file Browse button even though file can be entered manually - Finish button is enabled --------------------------------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-417 URL: https://jira.jboss.org/jira/browse/TEIIDDES-417 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 6.3 Environment: Iced Tea, Teiid Designer 6.3 Reporter: Paul Nittel Attachments: IMFTF.jpg I was writing a SWTBot test to create a view model's tables when I ran into this. Knowing SWTBot can't handle the File Chooser, I was delighted to see I could enter the text file's path and name directly into the importer dialog. It wasn't until some time later that I realized merely typing in the name does nothing; you MUST enter the name using the File Chooser. (Once that's been done, it appears you can use the drop-down to re-select that file, but you need that first time entry.) What's really bad/confusing is manually entering the file and target location enables the Finish button. Clicking it appears to work, but no tables were added to the model. -- 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

14 years, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-683) JDBC Importer cannot connect with DB unless the ConnectionProfile has username and password.

by John Doyle (JIRA)

JDBC Importer cannot connect with DB unless the ConnectionProfile has username and password. -------------------------------------------------------------------------------------------- Key: TEIIDDES-683 URL: https://jira.jboss.org/browse/TEIIDDES-683 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 7.1 Reporter: John Doyle Assignee: John Doyle The UI in the JDBC importer allows a user to provide a password at import time, rather than keep it in the ConnectionProfile, for security purposes. In theory DTP supports this use and has a connect() method that allows a user to pass the username and password. In practice there is a defect in the ConnectionProfiles provided in the DTP enablement project. The username and password are not used. This means that when a Teiid Designer user selects a ConnectionProfile w/o a password in the JDBC importer and supplies the password in our UI, the connection will fail. Here's the eclipse bug. https://bugs.eclipse.org/bugs/show_bug.cgi?id=328738 Targeted to be fixed in DTP 1.9. For our purposes the JDBC importer should validate that the profile has a password before attempting to connect, and inform the user that Teiid Designer can only use profiles with full credentials. -- 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

14 years, 5 months

3
7
0 / 0

[JBoss JIRA] Created: (TEIIDDES-631) Add REST Implementation for Generated Web Service War

by Ted Jones (JIRA)

Add REST Implementation for Generated Web Service War ----------------------------------------------------- Key: TEIIDDES-631 URL: https://jira.jboss.org/browse/TEIIDDES-631 Project: Teiid Designer Issue Type: Feature Request Reporter: Ted Jones Assignee: Ted Jones Fix For: 7.2 Need to add an option to generate a REST implementation of the generated web service war -- 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

14 years, 6 months

2
19
0 / 0

[JBoss JIRA] Created: (TEIIDDES-466) WSDL Generation from Web Service Models Creates Extraneous Nodes

by Ted Jones (JIRA)

WSDL Generation from Web Service Models Creates Extraneous Nodes ---------------------------------------------------------------- Key: TEIIDDES-466 URL: https://jira.jboss.org/browse/TEIIDDES-466 Project: Teiid Designer Issue Type: Task Components: Modeling Reporter: Ted Jones Assignee: Ted Jones Fix For: 7.0 Generated web service models from a Books VDB which creates operations for getBooks, getAuthors, getBooks_Authors, and getPublishers. A separate port type, binding and port is generated for each operation. Only one port type, binding and port is needed. We should get rid of the extraneous nodes and combine into one port type, binding and port. -- 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

14 years, 8 months

2
6
0 / 0

[JBoss JIRA] Created: (TEIIDDES-640) Exporting a relational to ddl, and turned off the comments option did not eliminate the comments from the ddl file.

by Van Halbert (JIRA)

Exporting a relational to ddl, and turned off the comments option did not eliminate the comments from the ddl file. ------------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-640 URL: https://jira.jboss.org/browse/TEIIDDES-640 Project: Teiid Designer Issue Type: Bug Components: Import/Export Reporter: Van Halbert Priority: Minor Fix For: 7.1.1 Using the export option to DDL, and changed the option to remove comments from being put into the ddl file, did not work. All the comments appeared there. -- 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

14 years, 9 months

3
12
0 / 0

[JBoss JIRA] Created: (TEIIDDES-518) DTP context menu options on Teiid tables should consider whether virtual model supports update.

by Ken Johnson (JIRA)

DTP context menu options on Teiid tables should consider whether virtual model supports update. ----------------------------------------------------------------------------------------------- Key: TEIIDDES-518 URL: https://jira.jboss.org/browse/TEIIDDES-518 Project: Teiid Designer Issue Type: Bug Affects Versions: 7.0 Environment: Teiid Designer 7.0 + JBoss Dev Studio 3.0.1GA Teiid 7.1 Alpha on EAP 5.1 RHEL 6, OpenJDK 1.6 Reporter: Ken Johnson In DTP, Context menu for Table contains several options under Data->(Edit, Load, Extract, Sample Contents). For virtual tables, Extract and Sample Contents are fine. Edit and Load will attempt to write data. Thus a few issues: a) These options should be disabled if the table in question does not have Supports Update checked. b) These options should be tested when the table *does* have Update and Insert procedures defined. c) Tables in SYS schema should never be writable. When working with physical tables, all options should be available and work correctly. Cursory testing indicates this is the case - at least with a MySQL data source underlying the 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

14 years, 9 months

2
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues October 2010