July 2009 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-209) New Text File or XML Connectors do not show up in Connectors View

by Barry LaFond (JIRA)

New Text File or XML Connectors do not show up in Connectors View ----------------------------------------------------------------- Key: TEIIDDES-209 URL: https://jira.jboss.org/jira/browse/TEIIDDES-209 Project: Teiid Designer Issue Type: Bug Affects Versions: 6.0.0, 6.1.0 Reporter: Barry LaFond Fix For: Future 1) Select "Text File Connector" in Connectors View 2) Right-click select "New" 3) Provide some name for new connector and click "OK" 4) New connector does not show up in Connectors View (under Text File Connector) 5) Selecting the "Hide Connector Types" action reveals the new connector There's a ConnectionBindingManager.geBindingsForType() method calling getBindingsForType() with a "filter flag = TRUE" causing the the binding check to use the Filtered map instead of non-filtered map. Not sure if this is intended or not. Javadoc says: "theFilterFlag the flag indicating if the result should be filtered to only include those that are supported by the DQP" -- 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

1
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-203) After importing the yahooconn.cdk, Designer "claims" the associated jar file is not needed

by Paul Nittel (JIRA)

After importing the yahooconn.cdk, Designer "claims" the associated jar file is not needed ------------------------------------------------------------------------------------------ Key: TEIIDDES-203 URL: https://jira.jboss.org/jira/browse/TEIIDDES-203 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 6.1.0 Environment: Fedora 10, JDK 1.6.0_10b33, Teiid Designer Snapshot from 6/2/09 Reporter: Paul Nittel I was following the instructions for the E2E Yahoo UDF Test Script. 1 - Start the Designer 2 - Create a project 3 - Import the cdk file 4 - Note the importer has also imported the jar file. Didn't do that. After selecting the cdk file, the import wizard reported, "1 connector type(s) and 0 connector(s) will be imported. No archive files need to be imported. Click 'Finish" to import." The connector type's properties include the correct name for the jar file. There were no exceptions. -- 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-201) Connector Binding Editor scroll bar does not allow you to scroll far enough if long properties are present.

by John Doyle (JIRA)

Connector Binding Editor scroll bar does not allow you to scroll far enough if long properties are present. ----------------------------------------------------------------------------------------------------------- Key: TEIIDDES-201 URL: https://jira.jboss.org/jira/browse/TEIIDDES-201 Project: Teiid Designer Issue Type: Bug Components: Editors Affects Versions: 6.1.0 Environment: Designer 6.1 running in IDE on RHEL CSB. Reporter: John Doyle The Connector Binding editor does not allow enough scrolling to see very long fields. For example, the XML-Relational SOAP Connector has a very long classpath (you have to display advanced properties), and there is no way to scroll to the end of it. -- 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-194) jdbc Oracle import does not create connector

by Luca Gioppo (JIRA)

jdbc Oracle import does not create connector -------------------------------------------- Key: TEIIDDES-194 URL: https://jira.jboss.org/jira/browse/TEIIDDES-194 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 6.0.0 Environment: eclipse.buildId=M20080911-1700 java.version=1.6.0_04 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=it_IT Command-line arguments: -os win32 -ws win32 -arch x86 Reporter: Luca Gioppo Importing model from jdbc Creating a new source for an Oracle 9 DB using jdbc14.jar and adding to udf (and a second time in the source definition) the jar from the oracle instant client the connection work, tables are imported but at hte end of the import the error is: Error post processing import (extension class=class com.metamatrix.modeler.internal.dqp.ui.jdbc.ConnectorBindingImportPostProcessor) -- 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-121) Simplify Adding Connector Jar as UDF jar in UDF view

by Barry LaFond (JIRA)

Simplify Adding Connector Jar as UDF jar in UDF view ---------------------------------------------------- Key: TEIIDDES-121 URL: https://jira.jboss.org/jira/browse/TEIIDDES-121 Project: Teiid Designer Issue Type: Feature Request Components: Views Affects Versions: 6.1.0 Reporter: Barry LaFond Priority: Minor Fix For: 6.1.0 Current UDF view provides two actions: Import UDF Extension Jars & Add Connector Jars to UDF The second action is somewhat redundant. Request moving the functionality of the second action into an "Advanced" section of the dialog from the first action. -- 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

1
1
0 / 0

[JBoss JIRA] Created: (TEIIDDES-174) Closing Project does not hide project-specific source bindings in Connectors View

by Barry LaFond (JIRA)

Closing Project does not hide project-specific source bindings in Connectors View --------------------------------------------------------------------------------- Key: TEIIDDES-174 URL: https://jira.jboss.org/jira/browse/TEIIDDES-174 Project: Teiid Designer Issue Type: Bug Components: Views Affects Versions: 6.0.0 Reporter: Barry LaFond Priority: Minor Fix For: Future 1) Import Books or Parts and verify Connectors and Source Binding is created in Connectors View 2) Right-click Project and "Close Project" 3) Source bindings still visible (should be removed) 4) Select/deselect the "Hide Connectors Types" button on Connectors view toolbar 5) Sources bindings are now hidden. 6) Re-open project and Source bindings now visible Problem with refresh on Connectors View during Project Close action. -- 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

1
1
0 / 0

[JBoss JIRA] Created: (TEIIDDES-190) There is no way to hand model a XML-Relational source.

by John Doyle (JIRA)

There is no way to hand model a XML-Relational source. ------------------------------------------------------ Key: TEIIDDES-190 URL: https://jira.jboss.org/jira/browse/TEIIDDES-190 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 6.0.0 Reporter: John Doyle Fix For: 6.1.1 We used to ship the model extensions for XML-R modeling with the importer, and now we generate them on demand with the importer. However, if a user needs to hand model from scratch, perhaps because there is no XSD, there is no model extension to depend on. We need to provide a way to create just the extension. -- 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

1
5
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

14 years, 5 months

2
7
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

14 years, 5 months

1
6
0 / 0

[JBoss JIRA] Created: (TEIIDDES-176) Desinger needs to embed "Teiid Embedded" as a plugin, with only dependencies to "public" APIs.

by Ramesh Reddy (JIRA)

Desinger needs to embed "Teiid Embedded" as a plugin, with only dependencies to "public" APIs. ---------------------------------------------------------------------------------------------- Key: TEIIDDES-176 URL: https://jira.jboss.org/jira/browse/TEIIDDES-176 Project: Teiid Designer Issue Type: Feature Request Components: Teiid Integration Reporter: Ramesh Reddy Assignee: Johnny Verhaeg Priority: Critical > On Wed, 2009-05-06 at 11:35 -0400, John Doyle wrote: >> I'm throwing this idea out there with very little idea of how the >> links between Teiid and Designer function, but I think it would be >> cool and beneficial. >> >> AFAIK we don't have a user story abut how you update the version of >> Teiid that is delivered with Designer. I think that it would be >> very cool if we exposed this cabability in designer similar to the >> way Installed JREs are exposed through the Preferences page. >> Designer could come with a version of Teiid, but users could point >> Designer to other versions of Teiid installed on their system and >> choose to run with those. One of the goals we have discussed is >> that we don't want Designer to be wedded to a particular version of >> Teiid. Defining the links between to two in this manner would >> force a contract and make it easy to test and validate that >> Designer 6.X works with Teiid 6.X and 7.X, etc. >> >> What do you think? > Well that is certainly the case going forward to have such modularity, > as this has been discussed before. However, that is not case today. > There needs to be huge re-work needs to be done in designer before we > can achieve this. Currently Designer knows too much about the Teiid's > configuration, that needs to be fixed such that it only communicates > only through the known public API like JDBC and Admin API. > > Ramesh.. -- 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, 6 months

3
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues July 2009