July 2011 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-553) Finish adding the "Name:Type" capability to procedures and the new Function model type

by Paul Nittel (JIRA)

Finish adding the "Name:Type" capability to procedures and the new Function model type -------------------------------------------------------------------------------------- Key: TEIIDDES-553 URL: https://jira.jboss.org/browse/TEIIDDES-553 Project: Teiid Designer Issue Type: Task Components: Modeling Affects Versions: 7.1 Environment: All Reporter: Paul Nittel When I'm modeling new relational models and creating columns, I can type the name of the column like "CoolColumnName:string(10)" and I not only get the column, I also get that its a String with a length of 10 characters. If I do that to a new Function model I get a column with the awkward name of "CoolColumnName:string(10)". Not valid! Please extend this valuable capability to other model type where applicable. -- 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

2
5
0 / 0

[JBoss JIRA] Created: (TEIIDDES-552) Function model should be automatically added to the VDB when a referencing model is added

by Paul Nittel (JIRA)

Function model should be automatically added to the VDB when a referencing model is added ----------------------------------------------------------------------------------------- Key: TEIIDDES-552 URL: https://jira.jboss.org/browse/TEIIDDES-552 Project: Teiid Designer Issue Type: Bug Components: VDB & Execution Affects Versions: 7.1 Environment: All Reporter: Paul Nittel Just like we automatically add XML Schema Documents (XSD) to a VDB when an XML document model is added, so should the function model when a referencing model is added. This will greatly increase the chance of first-time success! -- 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

2
1
0 / 0

[JBoss JIRA] Created: (TEIIDDES-477) Relationship Navigator view Focus pull-down is incorrectly sized

by Paul Nittel (JIRA)

Relationship Navigator view Focus pull-down is incorrectly sized ---------------------------------------------------------------- Key: TEIIDDES-477 URL: https://jira.jboss.org/browse/TEIIDDES-477 Project: Teiid Designer Issue Type: Bug Components: Views Affects Versions: 7.0 Environment: Teiid Designer 7.0.0 running in JBDS 3.0.1 Reporter: Paul Nittel While playing in the Relationship world, I noticed the Focus pulldown in the Relationship Navigator view is too small to see anything, and does not resize, even when the view is maximized in Eclipse. See attached screenshot. -- 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

2
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-923) Passing NULL into a Procedure in Preview Causes Exception

by Ted Jones (JIRA)

Passing NULL into a Procedure in Preview Causes Exception --------------------------------------------------------- Key: TEIIDDES-923 URL: https://issues.jboss.org/browse/TEIIDDES-923 Project: Teiid Designer Issue Type: Bug Components: Data Preview Affects Versions: 7.4 Reporter: Ted Jones I have a virtual procedure that accepts one parameter that may be null. When I pass a value in it works fine but when I check the NULL checkbox fir the input variable I get the following exception, "Remote org.teiid.api.exception.query.QueryValidatorException: Bind variables (represented as "?") were found but are allowed only in prepared or callable statements." Here is the generated query from preview: select * from ( exec RestfulBooks.getBooks(?) ) AS X_X -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-882) Create new SOAP service connection profile.

by John Doyle (JIRA)

Create new SOAP service connection profile. ------------------------------------------- Key: TEIIDDES-882 URL: https://issues.jboss.org/browse/TEIIDDES-882 Project: Teiid Designer Issue Type: Feature Request Components: Import/Export Affects Versions: 7.2, 7.1, 7.3 Reporter: John Doyle For the WSDL into Relational Model Importer we take advantage of the DTP provided Web Service Data Source connection profile. We really only did this because of time constraints. That profile has attributes that don't make sense for Teiid Designer and are ignored by Designer. We really need our own dedicated connection profile that provides the correct interface to the user and enables us to satisfy existing issues we cannot solve with the DTP profile. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

5
13
0 / 0

[JBoss JIRA] Created: (TEIIDDES-942) Need better indication of Error in Query Plan retrieval

by Mark Drilling (JIRA)

Need better indication of Error in Query Plan retrieval ------------------------------------------------------- Key: TEIIDDES-942 URL: https://issues.jboss.org/browse/TEIIDDES-942 Project: Teiid Designer Issue Type: Enhancement Components: Datatools Integration Affects Versions: 7.1.1 Reporter: Mark Drilling Priority: Minor It should be obvious to the user on the "Execution Plan" tab if a query error prevents retrieval of the Query Plan. - Executed a user query. The Execution Plan just showed the original SQL and nothing else... - Further examination of the server log showed plan debug output, but there was a source error on execution - I switched over to the "Message Log" tab in designer to find the message "An exception occurred fetching the Query Plan" Request that the Execution Plan tab show a problem message, instead of just showing the original SQL. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
2
0 / 0

[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

12 years, 2 months

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

12 years, 3 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues July 2011