February 2011 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-824) Wrong runtime-type generated during the XML transformation generation from XSD

by Ramesh Reddy (JIRA)

Wrong runtime-type generated during the XML transformation generation from XSD ------------------------------------------------------------------------------ Key: TEIIDDES-824 URL: https://issues.jboss.org/browse/TEIIDDES-824 Project: Teiid Designer Issue Type: Bug Components: Transformations Affects Versions: 7.2 Environment: F14 JBDS-CR2 Reporter: Ramesh Reddy 1) Imported the Books.xsd, BookDataTypes.xsd 2) Open the Books, xml schema and select "bibilography" element 3) Right click "Modeling -> Create XML to Scalar Transformation" The generated transformation for the "published" column is set as "gYear", thus the transformation validation fails. "gYear" is not a Teiid "runtime" data type. "gYear" is design time XML data type, however there are mappings defined for each design time data type to runtime type. I suspect, we are not doing the translations. For Teiid "gYear" should be mapped to "biginteger". Although "gYear" definition can not really map to biginteger (as it has optional timezone its definition), that how Teiid understands currently. We need to also make sure other 'g' types are also mapped correctly. If there is complex type that can not be deciphered correctly it may be good to leave as xml fragment. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

4
5
0 / 0

[JBoss JIRA] Created: (TEIIDDES-884) General Code Housekeeping for 7.4 release

by Barry LaFond (JIRA)

General Code Housekeeping for 7.4 release ----------------------------------------- Key: TEIIDDES-884 URL: https://issues.jboss.org/browse/TEIIDDES-884 Project: Teiid Designer Issue Type: Task Reporter: Barry LaFond -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-760) Add Teiid Designer SWTBot tests to the build process

by Pavol Srna (JIRA)

Add Teiid Designer SWTBot tests to the build process ---------------------------------------------------- Key: TEIIDDES-760 URL: https://issues.jboss.org/browse/TEIIDDES-760 Project: Teiid Designer Issue Type: Feature Request Components: Build Reporter: Pavol Srna New plugins with SWTBot tests for Teiid Designer were added. Please add these plug-ins to the build process. New plug-ins are located here: https://svn.jboss.org/repos/tdesigner/trunk/tests/org.teiid.designer.ui.b... https://svn.jboss.org/repos/tdesigner/trunk/tests/org.teiid.designer.ui.b... Note that there is a svn:externals property set on tests folder to resolve dependency of org.jboss.tools.ui.bot.ext -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 12 months

3
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-840) soften requirement limits in feature.xml <import> statements to ensure users can use DTP 1.7.x with latest Teiid 7.1.x

by Nick Boldt (JIRA)

soften requirement limits in feature.xml <import> statements to ensure users can use DTP 1.7.x with latest Teiid 7.1.x ---------------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-840 URL: https://issues.jboss.org/browse/TEIIDDES-840 Project: Teiid Designer Issue Type: Bug Components: Build Affects Versions: 7.1.1 Reporter: Nick Boldt Looking in branches/7.1/features/org.teiid.designer.runtime.feature/feature.xml, I see that you have very restrictive limits on required imported features: <requires> <import feature="org.eclipse.datatools.common.doc.user" version="1.7.0.v200908280400-26-311A16321A3557"/> <import feature="org.eclipse.datatools.connectivity.doc.user" version="1.7.0.v200908280400-37D-7733L3D753L7BBF"/> <import feature="org.eclipse.datatools.connectivity.feature" version="1.7.0.v200908280400-7B7OAIEn1XeacwFFi4FhDyooRMY"/> <import feature="org.eclipse.datatools.connectivity.oda.designer.feature" version="1.7.1.v200908280400-7E7C77DZRDEBDyIYEqgX"/> <import feature="org.eclipse.datatools.connectivity.oda.feature" version="1.7.1.v200908280400-7H794CcNBC0BvEdEXZe"/> <import feature="org.eclipse.datatools.doc.user" version="1.7.0.v200908280400-47C08w95ENAK6AFDFK7"/> <import feature="org.eclipse.datatools.enablement.apache.derby.feature" version="1.7.0.v200908280400-7768bBmKDLfMjHuIFJW7SBI"/> <import feature="org.eclipse.datatools.enablement.feature" version="1.7.0.v200908280400-7J8i2BWwQJOaz-Gi2C5seJM2FX2f"/> ... </requires> Wondering if you should explicitly include a match rule for the sake of clarity, and omit the qualifier/suffix so that you're not so brittle in your requirement. For example, could use one of these formats: <import plugin="org.eclipse.core.resources" version="3.2.0" match="compatible"/> or <import feature="org.hibernate.eclipse.feature" version="3.2.0" match="greaterOrEqual"/> -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-717) Designer whoudl provide option to create datasources during the VDB deploy

by Ramesh Reddy (JIRA)

Designer whoudl provide option to create datasources during the VDB deploy -------------------------------------------------------------------------- Key: TEIIDDES-717 URL: https://jira.jboss.org/browse/TEIIDDES-717 Project: Teiid Designer Issue Type: Feature Request Components: Teiid Integration Affects Versions: 7.1 Reporter: Ramesh Reddy Currently when a VDB is deployed, vdb is deployed but process does not check if the required data sources in the server exist or not. Designer should provide an option to the user to select to decide to create data sources or not in the same deploy action. This could be wizard driven if needed to. That way when a VDB is deployed all the required artifacts are also available in the server. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

3
6
0 / 0

[JBoss JIRA] Created: (TEIIDDES-859) Preview data failing for example project.

by Barry LaFond (JIRA)

Preview data failing for example project. ----------------------------------------- Key: TEIIDDES-859 URL: https://issues.jboss.org/browse/TEIIDDES-859 Project: Teiid Designer Issue Type: Feature Request Components: VDB & Execution Affects Versions: 7.3 Reporter: Barry LaFond Assignee: Barry LaFond Priority: Blocker Fix For: 7.3 Import Parts Example project Continue with example and try to preview or Execute VDB and get no "Source" error from Teiid. Problem is the Preview VDB is being created prior to the PartsSourceA.xmi being fully loaded. Result is the ModelEntry for it contains ModelType == "Type" instead of "Physical". Fix is to not respond to Open Project events in TEiid Designer "PreviewManager" class -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

3
9
0 / 0

[JBoss JIRA] Created: (TEIIDDES-877) Creating a new Teiid project does not open the Teiid Designer perspective

by John Doyle (JIRA)

Creating a new Teiid project does not open the Teiid Designer perspective ------------------------------------------------------------------------- Key: TEIIDDES-877 URL: https://issues.jboss.org/browse/TEIIDDES-877 Project: Teiid Designer Issue Type: Bug Components: Eclipse Integration Affects Versions: 7.2, 7.1.1 Environment: Teiid Designer in any Eclipse env. Reporter: John Doyle Assignee: John Doyle Fix For: 7.3 Creating a new Teiid project does not open the Teiid Designer perspective. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-768) Criteria Builder may insert crieria inside object names if user not careful

by Paul Nittel (JIRA)

Criteria Builder may insert crieria inside object names if user not careful --------------------------------------------------------------------------- Key: TEIIDDES-768 URL: https://issues.jboss.org/browse/TEIIDDES-768 Project: Teiid Designer Issue Type: Bug Components: Transformations Affects Versions: 7.1.1 Environment: JBDS 4.0 Beta2 Reporter: Paul Nittel I start with: CREATE VIRTUAL PROCEDURE BEGIN SELECT * FROM PartsSource.PARTS; END At this point the Criteria Builder (and Expression Builder) button is disabled. So I click in the SELECT clause to enable the button. Let's say I click between the P and the A of .PARTS. The button enables, I craft my WHERE clause, click OK and wind up with: CREATE VIRTUAL PROCEDURE BEGIN SELECT * FROM PartsSource.PA WHERE PartsSource.PARTS.PART_COLOR = PartsView.getPartsByColor.colorInRTS; END Regardless of where in the SELECT I click, the WHERE clause should be inserted in a syntactically correct location. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

4
5
0 / 0

[JBoss JIRA] Created: (TEIIDDES-710) Add Ability to Create Translator Overrides in Designer

by Ted Jones (JIRA)

Add Ability to Create Translator Overrides in Designer ------------------------------------------------------- Key: TEIIDDES-710 URL: https://jira.jboss.org/browse/TEIIDDES-710 Project: Teiid Designer Issue Type: Feature Request Components: VDB & Execution Affects Versions: 7.1 Reporter: Ted Jones Assignee: Ted Jones Need the ability to ad translator overrides for a VDB. Currently overrides have to be manually added to the vdb.xml. After talking with Barry, the best place for such and editor would be from the Translator field of the models table from within the VDB editor. There is a context menu that allows you to change the translator from that field. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

3
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-466) WSDL Generation from Web Service Models Creates Extraneous Nodes

by Ted Jones (JIRA)

WSDL Generation from Web Service Models Creates Extraneous Nodes ---------------------------------------------------------------- Key: TEIIDDES-466 URL: https://jira.jboss.org/browse/TEIIDDES-466 Project: Teiid Designer Issue Type: Task Components: Modeling Reporter: Ted Jones Assignee: Ted Jones Fix For: 7.0 Generated web service models from a Books VDB which creates operations for getBooks, getAuthors, getBooks_Authors, and getPublishers. A separate port type, binding and port is generated for each operation. Only one port type, binding and port is needed. We should get rid of the extraneous nodes and combine into one port type, binding and port. -- 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

15 years, 1 month

2
6
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues February 2011