September 2011 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-1043) Test Connection on LDAP Connection Profile Wizard page does not enable

by Barry LaFond (JIRA)

Test Connection on LDAP Connection Profile Wizard page does not enable ---------------------------------------------------------------------- Key: TEIIDDES-1043 URL: https://issues.jboss.org/browse/TEIIDDES-1043 Project: Teiid Designer Issue Type: Bug Components: Datatools Integration Affects Versions: 7.4, 7.5, 7.4.2 Reporter: Barry LaFond Fix For: 7.6 Filling in required info in new LDAP connection profile does not enable the "Test Connection" button. Looks like a "setPingButtonEnabled(true);" call needs to be made at the end of the LdapProfileDetailsWizardPage.validate() method, but adding the code ends up throwing an NPE when pressed. So, it looks like there is no IConnectionFactoryProvider/IConnectionFactory contributed for the LDAP connection to use to "ping" the DB. This would have to be completed in order for the Test Connection button to not throw an NPE -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

3
6
0 / 0

[JBoss JIRA] Created: (TEIIDDES-676) Add good defaults to XML Schema Import Wizard

by John Verhaeg (JIRA)

Add good defaults to XML Schema Import Wizard --------------------------------------------- Key: TEIIDDES-676 URL: https://jira.jboss.org/browse/TEIIDDES-676 Project: Teiid Designer Issue Type: Feature Request Components: Import/Export Affects Versions: 7.1 Reporter: John Verhaeg We should choose good defaults throughout this wizard, such as: - Pre-select the "from file system" option (vs. "via URL") on the first page - Auto-populate the "From directory" field to the user folder and remember whatever the user finally chooses thereafter. Working with a selection dialog that only allows you to choose a folder is too different from the norm to not be awkward. Always takes me a few seconds to remember why the *file* I'm trying to select is grayed-out. - Auto-populate the "Into folder" field if there is only one folder, a single project folder, in the workspace. - Provide a way to create a project so the user doesn't have to exit the entire wizard if they forget to first do that. -- 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

12 years, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-652) Rose importer fails with multiple exceptions

by Paul Nittel (JIRA)

Rose importer fails with multiple exceptions -------------------------------------------- Key: TEIIDDES-652 URL: https://jira.jboss.org/browse/TEIIDDES-652 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 7.1.1 Environment: JBDS H30 Reporter: Paul Nittel Fix For: 7.1.1 Attachments: NestedClass.mdl I used the Rose importer to import the attached .mdl file. I checked all objects as I progressed through the wizard. Eventually I received: Error 2010-10-06 10:26:05.71 java.lang.UnsupportedOperationException at org.eclipse.uml2.common.util.DerivedEObjectEList$DerivedListIterator.add(DerivedEObjectEList.java:278) at java.util.AbstractSequentialList.add(AbstractSequentialList.java:129) at org.eclipse.uml2.common.util.DerivedEObjectEList.addUnique(DerivedEObjectEList.java:636) at org.eclipse.uml2.common.util.DerivedEObjectEList.add(DerivedEObjectEList.java:623) at java.util.AbstractList.add(AbstractList.java:91) at com.metamatrix.rose.internal.handler.UmlHandler.createClass(UmlHandler.java:589) at com.metamatrix.rose.internal.handler.AbstractRoseHandler.visitObject(AbstractRoseHandler.java:239) at org.eclipse.emf.importer.rose.builder.RoseWalker.traverseObject(RoseWalker.java:45) at org.eclipse.emf.importer.rose.builder.RoseWalker.traverse(RoseWalker.java:63) at org.eclipse.emf.importer.rose.builder.RoseWalker.traverseList(RoseWalker.java:52) at org.eclipse.emf.importer.rose.builder.RoseWalker.traverse(RoseWalker.java:67) at org.eclipse.emf.importer.rose.builder.RoseWalker.traverseObject(RoseWalker.java:46) at org.eclipse.emf.importer.rose.builder.RoseWalker.traverse(RoseWalker.java:63) at org.eclipse.emf.importer.rose.builder.RoseWalker.traverseObject(RoseWalker.java:46) at org.eclipse.emf.importer.rose.builder.RoseWalker.traverse(RoseWalker.java:40) at com.metamatrix.rose.internal.RoseImporter.parseUnits(RoseImporter.java:869) at com.metamatrix.rose.internal.RoseImporter.parseSelectedUnits(RoseImporter.java:598) at com.metamatrix.rose.internal.ui.wizard.RoseImportWizard$4.run(RoseImportWizard.java:354) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) If a model is created it is incomplete. -- 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

12 years, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-585) Remove XML Service metamodel as it is no longer used.

by Ken Johnson (JIRA)

Remove XML Service metamodel as it is no longer used. ----------------------------------------------------- Key: TEIIDDES-585 URL: https://jira.jboss.org/browse/TEIIDDES-585 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 7.0 Environment: JBTools Aug 26, 2010. Eclipse 3.6, RHEL 6 Beta Reporter: Ken Johnson The XML Service metamodel is no longer used for sourcing XML data. It should be removed from Designer. -- 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

12 years, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (TEIIDDES-191) XSD as Relational importer has problems with child elements with many parents

by Greg Haber (JIRA)

XSD as Relational importer has problems with child elements with many parents ----------------------------------------------------------------------------- Key: TEIIDDES-191 URL: https://jira.jboss.org/jira/browse/TEIIDDES-191 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 6.0.0 Environment: Teiid Designer 6.0.0 official (14 May 2009) release Reporter: Greg Haber Attachments: address.xsd, person.xsd, person2.xml, person2.xsd I've encountered a lot of problems with the Teiid Designer XML as Relational Importer (and with its legacy ancestor) dealing with importing XSDs where a child element has multiple parents. The importer currently treats all elements throughout the XSD that have the same name and type as the same, and so models that element(s) as a single table with multiple parents, if the number of parents is above a configurable number (currently defaults to 3). Which is all well and good in theory, but in practice it seems to hit a number of problems 1) During the import process, if the selection of document root elements is left at the default, not all needed tables are generated. See person.xsd example attached. 2) If all possible root elements are selected, it looks mostly right, but there are often extra elements in the child tables (again try with person.xsd). Plus, the tables don't actually work at runtime correctly (try using attached person2.xml as the data source - notice that you can only get to the spouse's father from Person, not to their own father). I've also attached some other example problem XSDs - person2.xsd, and address.xsd Now, in some cases a reasonable workaround is to up the number of allowed parents parameter, so that everything gets folded into a single table. But that isn't a general solution, as it doesn't work with things like person2.xsd. -- 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

12 years, 5 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-1037) Data types inported from flat file partially implemented in wizard

by Paul Nittel (JIRA)

Data types inported from flat file partially implemented in wizard ------------------------------------------------------------------ Key: TEIIDDES-1037 URL: https://issues.jboss.org/browse/TEIIDDES-1037 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 7.5 Reporter: Paul Nittel The new Flat File metadata importer is great! Not having to write the TEXTTABLE function is a fine example of usability improvement. I noticed, during import, a dialog option that indicated datatypes can be the second line in the data file (column names being the first). That, and its associated help, are the only reference to this possibility (see attached screenshot). Without the actual functionality, it's confusing. Later in the wizardly process, the column names row number is captured. I suspect the types row--if present, and its use desired by the user--should also be determined at that point. The ability of importing the datatypes from the flat file would, IMHO, really enhance what is already a superb importer! (Yeah, I _do_ like it!) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

3
5
0 / 0

[JBoss JIRA] Created: (TEIIDDES-1079) Create Import VDB wizard

by Barry LaFond (JIRA)

Create Import VDB wizard ------------------------ Key: TEIIDDES-1079 URL: https://issues.jboss.org/browse/TEIIDDES-1079 Project: Teiid Designer Issue Type: Feature Request Components: Editors, Modeling, VDB & Execution Affects Versions: 7.5 Reporter: Barry LaFond Assignee: Barry LaFond Priority: Critical Fix For: 7.6 For usability improvements and migration support, it would be great to be able to import a VDB into a workspace, extract the models from the VDB into a new project (along with the VDB) and allow the user to begin to start editing the models as if they were new. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

2
6
0 / 0

[JBoss JIRA] Created: (TEIIDDES-1068) Import of Salesforce model does not map the BusinessHours table columns correctly

by Mark Drilling (JIRA)

Import of Salesforce model does not map the BusinessHours table columns correctly --------------------------------------------------------------------------------- Key: TEIIDDES-1068 URL: https://issues.jboss.org/browse/TEIIDDES-1068 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 7.4 Reporter: Mark Drilling Assignee: Mark Drilling Fix For: 7.6 Import from salesforce instance does appear to be mapping the BusinessHours column types correctly. The SundayStart,SundayEnd,MondayStart,MondayEnd,etc types should map to a time based datatype. It either does not get mapped or it maps to a string. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

4
5
0 / 0

[JBoss JIRA] Created: (TEIIDDES-1066) Enable editing of the translator override when its being created, the name is not editable

by Van Halbert (JIRA)

Enable editing of the translator override when its being created, the name is not editable ------------------------------------------------------------------------------------------ Key: TEIIDDES-1066 URL: https://issues.jboss.org/browse/TEIIDDES-1066 Project: Teiid Designer Issue Type: Feature Request Components: VDB & Execution Affects Versions: 7.4.2 Reporter: Van Halbert Building multiple vdb's in a single project, so that each will have different overrides to the translator in order to test various conditions. However, the translator override that is created for each vdb is called the same name (i.e,. <translator_name>-1), giving an illusion that properties maybe shared between the two. Unfortunately, was unable to change the name of the translator override so that each vdb override was specific. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

4
5
0 / 0

[JBoss JIRA] Created: (TEIIDDES-1081) Version 7.6 Release Work

by Barry LaFond (JIRA)

Version 7.6 Release Work ------------------------ Key: TEIIDDES-1081 URL: https://issues.jboss.org/browse/TEIIDDES-1081 Project: Teiid Designer Issue Type: Task Components: Build, Housekeeping Affects Versions: 7.6 Reporter: Barry LaFond Assignee: Barry LaFond Priority: Blocker Fix For: 7.6 All basic work related to 7.6 release -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues September 2011