December 2009 - teiid-designer-issues

[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

13 years, 9 months

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

13 years, 9 months

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

13 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

13 years, 9 months

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

13 years, 9 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

13 years, 10 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

13 years, 10 months

3
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-235) Order of operations problem in Designer

by Mark Drilling (JIRA)

Order of operations problem in Designer --------------------------------------- Key: TEIIDDES-235 URL: https://jira.jboss.org/jira/browse/TEIIDDES-235 Project: Teiid Designer Issue Type: Bug Components: Transformations Affects Versions: 6.0.0 Reporter: Mark Drilling The following query when entered into the transformation editor: select * from dips_view.cards LEFT OUTER JOIN CramerXRefData.CardTypes ON card = CardTypes.DIPS_CardType AND CramerXRefData.CardTypes.DIPS_ELEMTYPE IS NULL OR card = CardTypes.DIPS_CardType AND CramerXRefData.CardTypes.DIPS_ELEMTYPE = device_pk is parsed as; SELECT * FROM DIPS_View.Cards LEFT OUTER JOIN CramerXRefData.CardTypes ON ((CARD = DIPS_CARDTYPE) AND (DIPS_ELEMTYPE IS NULL)) OR ((CARD = DIPS_CARDTYPE) AND (DIPS_ELEMTYPE = Device_PK)) The ordering of different variations of CompoundCriteria are not preserved correctly. -- 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, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-168) Designer fails to delete project.

by John Doyle (JIRA)

Designer fails to delete project. --------------------------------- Key: TEIIDDES-168 URL: https://jira.jboss.org/jira/browse/TEIIDDES-168 Project: Teiid Designer Issue Type: Bug Affects Versions: 6.0.0 Environment: Designer 4-27 snapshot build on Fedora 10. Reporter: John Doyle I have two projects that models of the same name. When I try to delete the project in the Model Explorer, I am prompted that I am trying to delete a model when a model in another project depends upon it. As far as I can tell this is not true, and I'm surmising it's getting confused by the name. In any event, when I tell the designer to delete anyway, the delete does not happen. -- 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, 11 months

2
5
0 / 0

[JBoss JIRA] Created: (TEIIDDES-240) SFDC importer corrupts model during re-import, removing 'supports query' annotations on tables

by John Doyle (JIRA)

SFDC importer corrupts model during re-import, removing 'supports query' annotations on tables ---------------------------------------------------------------------------------------------- Key: TEIIDDES-240 URL: https://jira.jboss.org/jira/browse/TEIIDDES-240 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 6.0.0, 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

14 years, 3 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues December 2009