April 2011 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-631) Add REST Implementation for Generated Web Service War

by Ted Jones (JIRA)

Add REST Implementation for Generated Web Service War ----------------------------------------------------- Key: TEIIDDES-631 URL: https://jira.jboss.org/browse/TEIIDDES-631 Project: Teiid Designer Issue Type: Feature Request Reporter: Ted Jones Assignee: Ted Jones Fix For: 7.2 Need to add an option to generate a REST implementation of the generated web service war -- 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, 5 months

2
19
0 / 0

[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, 5 months

4
5
0 / 0

[JBoss JIRA] Created: (TEIIDDES-944) Add Teiid Server 7.4 Connection Profile Driver definition

by Barry LaFond (JIRA)

Add Teiid Server 7.4 Connection Profile Driver definition --------------------------------------------------------- Key: TEIIDDES-944 URL: https://issues.jboss.org/browse/TEIIDDES-944 Project: Teiid Designer Issue Type: Sub-task Components: Datatools Integration Affects Versions: 7.4 Reporter: Barry LaFond Assignee: Dan Florian Priority: Blocker Fix For: 7.4 7.4 release needs to be compatible with Teiid 7.4 client. So we need to add a new driver definition to the org.teiid.datatools.connectivity plugin.xml and any additional artifacts or definitions. Result should be that 7.4 Designer Preview Data and Execute VDB actions create/use a 7.4 Driver definition BUT the option in DTP to create a 7.1 Teiid driver is available. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

3
3
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, 5 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-945) Add generic extension metadata handling

by Steven Hawkins (JIRA)

Add generic extension metadata handling --------------------------------------- Key: TEIIDDES-945 URL: https://issues.jboss.org/browse/TEIIDDES-945 Project: Teiid Designer Issue Type: Feature Request Components: Modeling Reporter: Steven Hawkins Relational models in particular would benefit from the ability to add/edit/remove name value pairs on all indexable records that can have extension metadata. This includes things like tables/procedures/columns and excludes schemas/catalogs. The name value pairs should appear in the index file just like an actual extension property. No validation is needed on either the keys or the values at this time. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

3
9
0 / 0

[JBoss JIRA] Created: (TEIIDDES-941) Imported Model Project with user defined Function model does not register function model with Function Library

by Barry LaFond (JIRA)

Imported Model Project with user defined Function model does not register function model with Function Library -------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-941 URL: https://issues.jboss.org/browse/TEIIDDES-941 Project: Teiid Designer Issue Type: Bug Components: Import/Export, Modeling Affects Versions: 7.4 Reporter: Barry LaFond Assignee: Barry LaFond Priority: Blocker Fix For: 7.4 Imported FinancialsDemo.zip model project into workspace in 7.4 workspace. Got 2 "problems" and one of them resulted from transformation validation not understanding the hashToPII(string ID) function/method. I edited the function model and "saved" it, then did clean build and problem went away. The import process (opening project) is not resulting in the custom function model being registered in the Function Library. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

1
7
0 / 0

[JBoss JIRA] Created: (TEIIDDES-933) UDFs should be targets in the role permission editor

by Steven Hawkins (JIRA)

UDFs should be targets in the role permission editor ---------------------------------------------------- Key: TEIIDDES-933 URL: https://issues.jboss.org/browse/TEIIDDES-933 Project: Teiid Designer Issue Type: Enhancement Components: Modeling Affects Versions: 7.4 Reporter: Steven Hawkins See SOA-3015 and TEIID-1550. Udfs should be treated just like stored procedures in the permission editor. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

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

14 years, 6 months

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

14 years, 6 months

3
6
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues April 2011