December 2011 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1109) Error while validating Web service operation transformation points to source in underlying error-free model

by Paul Nittel (Created) (JIRA)

Error while validating Web service operation transformation points to source in underlying error-free model ----------------------------------------------------------------------------------------------------------- Key: TEIIDDES-1109 URL: https://issues.jboss.org/browse/TEIIDDES-1109 Project: Teiid Designer Issue Type: Bug Components: Validation Affects Versions: 7.4.2 Reporter: Paul Nittel Priority: Critical I'm executing the Updateable Web Service test and have encountered a new error. I'm working on the operation that does inserts. The SQL is sending the update info to the view model that has the INSERT transformation. When I validate the procedure, I get ERROR: Products.PRODUCTSYMBOLS does not exist. That actually exists as a source underlying the Updates model, not the Web Service. So how can the underlying transformation be valid and this one not be? (At least relative to this particular table in question.) I'd be happy to find out it was something I did incorrectly, but the error message is pretty weak in conveying meaningful information. Given the ubiquitous nature of Web services, I'm marking this bug as "critical". It could be a blocker, but I'll let someone else make that call. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

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

13 years

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

13 years

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

13 years

2
4
0 / 0

[JBoss JIRA] (TEIIDDES-1205) Reminder to deprecate the old extension framework for later removal

by Van Halbert (Created) (JIRA)

Reminder to deprecate the old extension framework for later removal ------------------------------------------------------------------- Key: TEIIDDES-1205 URL: https://issues.jboss.org/browse/TEIIDDES-1205 Project: Teiid Designer Issue Type: Task Components: Documentation Affects Versions: 7.7 Reporter: Van Halbert Priority: Critical Fix For: 7.7 Deprecate the old extension framework so that it can be removed in a later release (i.e, 8.0). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

4
7
0 / 0

[JBoss JIRA] (TEIIDDES-1175) Importing a new model when an existing model is selected in the modeler tree works, but leaves old model info in Data Source props

by Paul Nittel (Created) (JIRA)

Importing a new model when an existing model is selected in the modeler tree works, but leaves old model info in Data Source props ---------------------------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-1175 URL: https://issues.jboss.org/browse/TEIIDDES-1175 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 7.6 Environment: Fedora 16 Reporter: Paul Nittel Attachments: ShouldBeOracleSourceInfo.png I imported from a DB2 source. With that model selected, I right-clicked elsewhere in the Model Explorer tree and imported a different model. At the last page of the import wizard, the previously-selected model was the targeted name for this new model. I unchecked update and changed the name of the model to reflect what was being imported. After the import had completed, the Data Source item for the imported model had the information from the old model which had been selected in the tree. See attached screenshot. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

5
5
0 / 0

[JBoss JIRA] (TEIIDDES-1098) Procedure parameter name refactoring issues

by Steven Hawkins (Created) (JIRA)

Procedure parameter name refactoring issues ------------------------------------------- Key: TEIIDDES-1098 URL: https://issues.jboss.org/browse/TEIIDDES-1098 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 7.4.2 Reporter: Steven Hawkins Priority: Minor I encountered a couple of issues when refactoring a procedure parameter name. 1. The procedure transformation sql is not updated with the new name. For example given a procedure with a parameter param and a definition that just returns that value: CREATE VIRTUAL PROCEDURE BEGIN SELECT param AS foo; END refactoring to param1 leaves the select as "select param as foo" rather than updating to select param1 as foo. Note that if this is implemented, then aliases may need to be added to, e.g. "select param" would become "select param1 as param". There is existing logic in the Teiid ExpressionMappingVisitor to handle that. 2. If you undo the refactoring of the name, then even after a save and rebuild the model is still marked with an error. I had to edit the already valid SQL to clear the error. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

4
6
0 / 0

[JBoss JIRA] (TEIIDDES-1204) XmlProfileDetailsWizardPage.NotXmlUrl.Message not found in i18n properties

by Van Halbert (Created) (JIRA)

XmlProfileDetailsWizardPage.NotXmlUrl.Message not found in i18n properties --------------------------------------------------------------------------- Key: TEIIDDES-1204 URL: https://issues.jboss.org/browse/TEIIDDES-1204 Project: Teiid Designer Issue Type: Bug Components: Datatools Integration Affects Versions: 7.7 Reporter: Van Halbert Assignee: Barry LaFond Priority: Minor XmlProfileDetailsWizardPage.NotXmlUrl.Message not found in i18n properties -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

4
6
0 / 0

[JBoss JIRA] (TEIIDDES-1200) Synchronizing a VDB takes too long in 7.4.2

by Debbie Steigner (Created) (JIRA)

Synchronizing a VDB takes too long in 7.4.2 ------------------------------------------- Key: TEIIDDES-1200 URL: https://issues.jboss.org/browse/TEIIDDES-1200 Project: Teiid Designer Issue Type: Bug Components: Validation, VDB & Execution Affects Versions: 7.4.2 Reporter: Debbie Steigner Synchronizing a big VDB in version 7.4.2 (JBDS 4.1.1) takes 30 minutes versus 2 minutes in 7.1.1 (JBDS 4.1.0) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

6
22
0 / 0

[JBoss JIRA] (TEIIDDES-1192) Import Flat File Source >> Source and View Model places model in root directory and not selected sub-directories

by Blaine Mincey (Created) (JIRA)

Import Flat File Source >> Source and View Model places model in root directory and not selected sub-directories ---------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-1192 URL: https://issues.jboss.org/browse/TEIIDDES-1192 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 7.4 Environment: RHEL 6.1 (CSB), Sun/Oracle Java 1.6.0_29, JBDS 4.1.1 Reporter: Blaine Mincey When using the new flat file importer, the source and view models are placed in the root directory of the project and not in the selected sub-directories. For example, if I create a new Teiid Project. Then, create a folder for DataSources and a folder for VirtualBaseLayer. When I import the flat file, the last window in the dialogue prompts for where the Source and View models should be placed. If I select the DataSources for source and the VirtualBaseLayer for View, the models are dropped in the root folder of the project and not in the selected sub-directories. I currently work around this by refactoring the models and "moving" them to the appropriate locations. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

6
7
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues December 2011