June 2011 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-530) The LDAP documentation in MMx that relates to designer activity, needs to be included in the designer documentation

by Van Halbert (JIRA)

The LDAP documentation in MMx that relates to designer activity, needs to be included in the designer documentation ------------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-530 URL: https://jira.jboss.org/browse/TEIIDDES-530 Project: Teiid Designer Issue Type: Task Components: Documentation Affects Versions: 7.0 Reporter: Van Halbert There is MMx LDAP documentation that relates to what has to be done in the designer in order to model a LDAP data source. This documentation needs to be brought over into designer documentation. -- 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
1
0 / 0

[JBoss JIRA] Created: (TEIIDDES-579) SQL Scrapbook created from Teiid connection is created with Ingress_2006 as the Connection Profile type.

by John Doyle (JIRA)

SQL Scrapbook created from Teiid connection is created with Ingress_2006 as the Connection Profile type. -------------------------------------------------------------------------------------------------------- Key: TEIIDDES-579 URL: https://jira.jboss.org/browse/TEIIDDES-579 Project: Teiid Designer Issue Type: Bug Components: Eclipse Integration Affects Versions: 7.1 Reporter: John Doyle Assignee: John Doyle Fix For: 7.1 If you right click on a Teiid connection in the Data Source Explorer and open a SQL Scrapbook, the scrapbook page is not created with a Teiid Connection Profile Type, it is created with an Ingress_2006 type. -- 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

3
6
0 / 0

[JBoss JIRA] Created: (TEIIDDES-971) In Designer, when importing tables with foreign keys, let user bring in tables without foreign key dependency errors / allow override

by Joel Tosi (JIRA)

In Designer, when importing tables with foreign keys, let user bring in tables without foreign key dependency errors / allow override ------------------------------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-971 URL: https://issues.jboss.org/browse/TEIIDDES-971 Project: Teiid Designer Issue Type: Enhancement Components: Import/Export Affects Versions: 7.2 Environment: JBDS 4.0 Reporter: Joel Tosi When mapping data in side Designer, a user is forced to bring in all dependencies (think tables with foreign key dependencies) in order to have a valid model. You should be able to override this - make the user aware of the missing data and allow user to accept the limitation. Think of a scenario where there is a large database, with say 100 tables. Tons of foreign keys, etc. If a user wants to create a model against one table that has one foreign key (and bringing in its dependency brings another foreign key....etc) - if the user doesn't need the information from the related table for their modeling, then they should be allowed to override the warning and model without the dependency. To reproduce - create a relational store and create 10 tables (A - J) - A has a foreign key to B, B to C, and so on. In designer, be able to override the warning when trying to model against just A. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

4
5
0 / 0

[JBoss JIRA] Created: (TEIIDDES-597) Insert Rows in relational column table editor creates columns in reverse order

by Paul Nittel (JIRA)

Insert Rows in relational column table editor creates columns in reverse order ------------------------------------------------------------------------------ Key: TEIIDDES-597 URL: https://jira.jboss.org/browse/TEIIDDES-597 Project: Teiid Designer Issue Type: Bug Components: Editors Affects Versions: 7.1 Environment: All Reporter: Paul Nittel Fix For: 7.1.1 Attachments: OutOfOrder.png (This has been an issue for a long time, but I don't see a current bug, so here's a new one!) If a user chooses to edit relational columnar metadata in teh table editor and Inserts Rows, they are inserted in reverse order. (See the attached screenshot.) In this case I inserted 8 rows. They're shown int eh tree in the correct order but arte inverted in the table editor. It's just wrong. -- 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

3
5
0 / 0

[JBoss JIRA] Created: (TEIIDDES-908) Replace Salesforce Extension Model created during import

by Barry LaFond (JIRA)

Replace Salesforce Extension Model created during import --------------------------------------------------------- Key: TEIIDDES-908 URL: https://issues.jboss.org/browse/TEIIDDES-908 Project: Teiid Designer Issue Type: Enhancement Components: Import/Export Affects Versions: 7.3 Reporter: Barry LaFond Assignee: Barry LaFond Priority: Blocker Fix For: 7.4 In order to simplify JDBC import processing by replacing Designer's RelationalModelProcessor with Teiid's processor, the Salesforce Import use-case needs to be simplified by removing the need to have a separate Extension model. TEIIDDES-905 is providing a new extension model framework that eliminates the need for a separate model. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

3
14
0 / 0

[JBoss JIRA] Created: (TEIIDDES-926) Create persistance and loading mechanism for XML-based Model Extension Definitions

by Barry LaFond (JIRA)

Create persistance and loading mechanism for XML-based Model Extension Definitions ---------------------------------------------------------------------------------- Key: TEIIDDES-926 URL: https://issues.jboss.org/browse/TEIIDDES-926 Project: Teiid Designer Issue Type: Sub-task Components: Import/Export, Modeling Affects Versions: 7.4 Reporter: Barry LaFond Assignee: Dan Florian Priority: Blocker Fix For: 7.4 Attachments: modelExtension.xsd, salesforce.mxd The New Model Extension framework requires reading (loading) and writing XML-formatted Model Extension Definition properties. These property definitions will replace the old "Extension Model" EMF construct. Attached is a sample "salesforce.mxd" (Model eXtension Definition) file and a potential backing schema -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

2
17
0 / 0

[JBoss JIRA] Created: (TEIIDDES-972) When importing an existing model, message notes that this is an existing model but 'Update' is not chosen by default

by Joel Tosi (JIRA)

When importing an existing model, message notes that this is an existing model but 'Update' is not chosen by default -------------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-972 URL: https://issues.jboss.org/browse/TEIIDDES-972 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 7.2 Environment: JBDS 4.0 Reporter: Joel Tosi Priority: Minor Create a model against a relational store. Do some modeling against it Choose to import the model again Note the warning message states that the model already exists Note that the update checkbox is not checked Expected outcome is that since the message knows it is an update, the update checkbox would be checked by default -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-984) Create or update existing Test Scripts with artifacts

by Barry LaFond (JIRA)

Create or update existing Test Scripts with artifacts ----------------------------------------------------- Key: TEIIDDES-984 URL: https://issues.jboss.org/browse/TEIIDDES-984 Project: Teiid Designer Issue Type: Task Components: Documentation Affects Versions: 7.5 Reporter: Barry LaFond Priority: Critical Fix For: 7.5 Several of the E2E and integration test scripts are outdated and need to be improved and/or cleaned up. In addition, these scripts are used by QE to create SWT Bot tests. This jira is parent task to spend some time in 7.5 release to provide up-to-date or new scripts along with compatible artifacts (XMI models, VDB's, XML Schema files, *.txt files) that can be used to create automated SWT Bot tests and to assist in better milestone and release testing. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-714) Designer should clean up preview vdbs every time Teiid Server connection is made.

by Ramesh Reddy (JIRA)

Designer should clean up preview vdbs every time Teiid Server connection is made. --------------------------------------------------------------------------------- Key: TEIIDDES-714 URL: https://jira.jboss.org/browse/TEIIDDES-714 Project: Teiid Designer Issue Type: Bug Components: Teiid Integration Affects Versions: 7.1 Reporter: Ramesh Reddy It is quite possible that that the preview vdbs deployed into a Teiid Server get out of sync with the Designer when the Server is restarted independent of the Designer. Since Designer keeps track of its preview vdbs based on workspace uuid, it is better that it cleans up its preview vdbs and data sources when the connection is made and connection is cleaned up. These actions may happen at both startup and shutdown of the Designer and also at the creation and discard of the Server settings once the Designer started. Otherwise there may be orphan VDBs left over in the Server. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

2
7
0 / 0

[JBoss JIRA] Created: (TEIIDDES-704) NPE while constructing XML Documents from old/custom Parts XML Schema

by Barry LaFond (JIRA)

NPE while constructing XML Documents from old/custom Parts XML Schema --------------------------------------------------------------------- Key: TEIIDDES-704 URL: https://jira.jboss.org/browse/TEIIDDES-704 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 7.1.1 Reporter: Barry LaFond Fix For: 7.2 TEIIDDES-664 exposed a problem with displaying a error dialog when XML Document creation fails. This was fixed. What's not fixed is the NPE that is resulting from the schema involved. See attached Schema and create an XML Document from the PartOrder root element. Exception in thread "ModelBuffer.Save" java.lang.NullPointerException at org.eclipse.emf.ecore.xmi.impl.XMLHelperImpl.getURIFragment(XMLHelperImpl.java:719) at org.eclipse.emf.ecore.xmi.impl.XMLHelperImpl.getIDREF(XMLHelperImpl.java:753) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveIDRefSingle(XMLSaveImpl.java:1972) at com.metamatrix.modeler.internal.core.resource.xmi.MtkXmiSaveImpl.saveIDRefSingle(MtkXmiSaveImpl.java:298) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveFeatures(XMLSaveImpl.java:1318) at com.metamatrix.modeler.internal.core.resource.xmi.MtkXmiSaveImpl.saveElementID(MtkXmiSaveImpl.java:248) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveElement(XMLSaveImpl.java:1174) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveElement(XMLSaveImpl.java:1035) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveContainedMany(XMLSaveImpl.java:2386) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveFeatures(XMLSaveImpl.java:1533) at com.metamatrix.modeler.internal.core.resource.xmi.MtkXmiSaveImpl.saveElementID(MtkXmiSaveImpl.java:248) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveElement(XMLSaveImpl.java:1174) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveElement(XMLSaveImpl.java:1035) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveContainedMany(XMLSaveImpl.java:2386) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveFeatures(XMLSaveImpl.java:1533) at com.metamatrix.modeler.internal.core.resource.xmi.MtkXmiSaveImpl.saveElementID(MtkXmiSaveImpl.java:248) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveElement(XMLSaveImpl.java:1174) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveElement(XMLSaveImpl.java:1035) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveContainedMany(XMLSaveImpl.java:2386) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveFeatures(XMLSaveImpl.java:1533) at com.metamatrix.modeler.internal.core.resource.xmi.MtkXmiSaveImpl.saveElementID(MtkXmiSaveImpl.java:248) at org.eclipse.emf.ecore.xmi.impl.XMISaveImpl.writeTopObjects(XMISaveImpl.java:90) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.traverse(XMLSaveImpl.java:592) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.save(XMLSaveImpl.java:256) at org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.doSave(XMLResourceImpl.java:206) at com.metamatrix.modeler.internal.core.resource.xmi.MtkXmiResourceImpl.doSave(MtkXmiResourceImpl.java:354) at org.eclipse.emf.ecore.resource.impl.ResourceImpl.save(ResourceImpl.java:1406) at com.metamatrix.modeler.internal.core.workspace.ModelBufferImpl.saveInTransaction(ModelBufferImpl.java:559) at com.metamatrix.modeler.internal.core.workspace.ModelBufferImpl$1.run(ModelBufferImpl.java:488) -- 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

1
4
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues June 2011