November 2011 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-987) Add ability to edit/generate Create Virtual Procedure statements for RestEasy XML, File Translator and Web Service Translator procedures

by Barry LaFond (JIRA)

Add ability to edit/generate Create Virtual Procedure statements for RestEasy XML, File Translator and Web Service Translator procedures ---------------------------------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-987 URL: https://issues.jboss.org/browse/TEIIDDES-987 Project: Teiid Designer Issue Type: Enhancement Components: Editors, Transformations Affects Versions: 7.4 Reporter: Barry LaFond Fix For: 7.5 Designer includes "Generate xxxx procedures" options in the New Model Wizard. Also have a RestEasy use-case that requires getXXXX virtual procedures that contain SQL like: CREATE VIRTUAL PROCEDURE BEGIN SELECT XMLELEMENT(NAME parts, XMLAGG(XMLELEMENT(NAME part, XMLFOREST(VirtualParts_Supplier.PARTS.PART_ID, VirtualParts_Supplier.PARTS.PART_NAME, VirtualParts_Supplier.PARTS.PART_COLOR, VirtualParts_Supplier.PARTS.PART_WEIGHT)))) AS result FROM VirtualParts_Supplier.PARTS WHERE VirtualParts_Supplier.getParts.partId_in = VirtualParts_Supplier.PARTS.PART_ID; END Would be nice to have a framework where "wizards" can be accessed to create/edit the content of this SQL if the basic structure is a Set Query (SELECT * FROM XXX)for these specific use-cases. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
9
0 / 0

[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

14 years, 2 months

3
6
0 / 0

[JBoss JIRA] (TEIIDDES-1165) MED Editor Properties page should utilize same "Model Class" and "Model Type" combo boxes as the New Metadata Model wizard.

by Barry LaFond (Created) (JIRA)

MED Editor Properties page should utilize same "Model Class" and "Model Type" combo boxes as the New Metadata Model wizard. --------------------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-1165 URL: https://issues.jboss.org/browse/TEIIDDES-1165 Project: Teiid Designer Issue Type: Enhancement Reporter: Barry LaFond Assignee: Dan Florian The properties tab currently presents a metamodel URI combo box, but we've been trying to get away from EMF. The New Model wizard displays only the simple Model Class and Model Type values. We'd of course, limit the Model Classes to Relational, XML Document, Web Services and Function models. Model types would be Source, View and in the case of Function model, "User Defined Function" model type. Without the Model Type selection, which is currently missing, users won't be able to target or limit applying properties to specific model types. The REST extension properties, for instance is only applicable to "View" models. It's MED should include supported Model Types list to include only View + Relational. We probably need to allow a third Relational model type of "BOTH", so an MED wouldn't have to be created for both metamodels? -- 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

14 years, 3 months

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

14 years, 3 months

2
2
0 / 0

[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

14 years, 3 months

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

14 years, 3 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

14 years, 3 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

14 years, 3 months

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

14 years, 3 months

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

14 years, 3 months

4
6
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues November 2011