July 2010 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-515) Remove Version From Teiid Jars in Embedded Teiid Embedded Query

by Ted Jones (JIRA)

Remove Version From Teiid Jars in Embedded Teiid Embedded Query --------------------------------------------------------------- Key: TEIIDDES-515 URL: https://jira.jboss.org/browse/TEIIDDES-515 Project: Teiid Designer Issue Type: Task Reporter: Ted Jones Fix For: 7.1 I propose we remove the version number from the Teiid jars in the Teiid Embedded Query project. I have a dependency on the client jar when programmatically compiling my java files for the JBossWS-CXF war and the version number requires hard-coding for every release. The admin api also depends on the Teiid jars. -- 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, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-265) Reimplement binding creation for the WSDL to Relational importer around new admin API.

by John Doyle (JIRA)

Reimplement binding creation for the WSDL to Relational importer around new admin API. -------------------------------------------------------------------------------------- Key: TEIIDDES-265 URL: https://jira.jboss.org/jira/browse/TEIIDDES-265 Project: Teiid Designer Issue Type: Task Components: Import/Export Affects Versions: 7.0 Reporter: John Doyle Assignee: John Doyle Fix For: 7.0 Recreate the binding creation code when the new Teiid admin API is integrated. -- 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, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-430) Create Web Service War Wizard

by Ted Jones (JIRA)

Create Web Service War Wizard ----------------------------- Key: TEIIDDES-430 URL: https://jira.jboss.org/jira/browse/TEIIDDES-430 Project: Teiid Designer Issue Type: Feature Request Components: Modeling Reporter: Ted Jones Fix For: 7.0 Need a wizard to create a JBossWS-CXF war based off wsdl and schemas used for web service model(s). This is tied to https://jira.jboss.org/jira/browse/TEIID-1034. -- 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, 4 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-267) UDF-related changes

by Barry LaFond (JIRA)

UDF-related changes ------------------- Key: TEIIDDES-267 URL: https://jira.jboss.org/jira/browse/TEIIDDES-267 Project: Teiid Designer Issue Type: Sub-task Components: Teiid Integration Affects Versions: 7.0 Reporter: Barry LaFond Assignee: Dan Florian Priority: Blocker Fix For: 7.0 Teiid 7.0 has changed their UDF-related code requiring re-integrating their new framework into Designer. FunctionLibraryManager doesn't exist anymore, FunctionLibrary has changed. 1) Investigate changes to Teiid and how Designer is supposed to handle UDF models in workspace. -- 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, 4 months

1
6
0 / 0

[JBoss JIRA] Created: (TEIIDDES-461) VDB Editor needs framework to display context actions for selected model entries

by Barry LaFond (JIRA)

VDB Editor needs framework to display context actions for selected model entries -------------------------------------------------------------------------------- Key: TEIIDDES-461 URL: https://jira.jboss.org/browse/TEIIDDES-461 Project: Teiid Designer Issue Type: Task Components: Editors, VDB & Execution Affects Versions: 7.0 Reporter: Barry LaFond Priority: Critical Fix For: 7.0 The VDB editor provides textual place-holders for translator-name and JNDI (data source) name. TEIIDDES-404 involves providing a Deploy VDB action to a desired Teiid Server instance. To facilitate this deployment, the "translator-name" and "JNDI" names have to match names of existing Translators and Data Sources on the desired server. So the VDB Editor needs to provide the hooks/actions to allow the user to "select" these items from the desired server. The VDB Editor needs to provide a context menu on selection of a row/cell in the model entry table. Upon right-click, the "fillContextMen()" call or something like that will query the SourceHandlerExtensionManager for a list of available actions which will be contributed via the VdbSourceHandler contribution in DQP plugin. Two actions will be returned to display for the user, 1) "Select Translator" and 2) "Select Data Source". Note that during these actions, the user will first have to "pick" or "connect" to a Teiid Instance. -- 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, 4 months

2
6
0 / 0

[JBoss JIRA] Created: (TEIIDDES-406) Design Time Role Management

by Barry LaFond (JIRA)

Design Time Role Management --------------------------- Key: TEIIDDES-406 URL: https://jira.jboss.org/jira/browse/TEIIDDES-406 Project: Teiid Designer Issue Type: Feature Request Components: Modeling, Teiid Integration, VDB & Execution Affects Versions: 7.0 Reporter: Barry LaFond Priority: Critical Fix For: 7.0 Role management in "Metamatrix" days was done via it's console. Today, JOPR/JON provides the console-type functionality. However, the data-role management is being pushed down to design-time. So Designer needs to take this on, allow data roles (authorization/entitlements) at the column, table and model levels. In addition there needs to be a way to manage higher-level "security" roles that will be mapped to actual roles when VDB's are deployed to the server. This will required injecting these roles into the VDB for transport and eventual mapping. -- 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, 4 months

1
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-496) Corretly fix NULL string value issues with VDB Editor. In particular, JNDI Name and Description values

by Barry LaFond (JIRA)

Corretly fix NULL string value issues with VDB Editor. In particular, JNDI Name and Description values ------------------------------------------------------------------------------------------------------ Key: TEIIDDES-496 URL: https://jira.jboss.org/browse/TEIIDDES-496 Project: Teiid Designer Issue Type: Bug Affects Versions: 7.0 Reporter: Barry LaFond Assignee: Johnny Verhaeg Priority: Blocker Fix For: 7.0 VDB Editor is not handling NULL string values correctly for JNDI name and Description. The current fix addresses the problem at the wrong level (i.e. VdbModelEntry). Needs to get fixed in the UI components. -- 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, 4 months

2
7
0 / 0

[JBoss JIRA] Created: (TEIIDDES-470) Create framework to manage data/security roles at design-time

by John Verhaeg (JIRA)

Create framework to manage data/security roles at design-time ------------------------------------------------------------- Key: TEIIDDES-470 URL: https://jira.jboss.org/browse/TEIIDDES-470 Project: Teiid Designer Issue Type: Feature Request Components: Modeling, VDB & Execution Affects Versions: 6.3 Reporter: John Verhaeg Fix For: 7.1 Scope of roles need to be at least VDB-level, possibly project or workspace level. Roles need to automatically be imported into VDBs when VDBs are created. -- 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, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-227) Errors when importing procedures from relational (Oracle) source

by Paul Nittel (JIRA)

Errors when importing procedures from relational (Oracle) source ---------------------------------------------------------------- Key: TEIIDDES-227 URL: https://jira.jboss.org/jira/browse/TEIIDDES-227 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 6.2.0 Environment: fedora 10, Designer 6.2 RC1 Reporter: Paul Nittel I tried to import the procedures from the Oracle 10g BQT source and ran into a set of problems. 1 - At the end of the import, a dialog is shown that proclaims the import failed (Unabled to import model into workspace. See log for details). Yes, it does say, "Unabled." In the log file there was this NPE: !ENTRY org.teiid.designer.jdbc.relational 4 3003 2009-09-22 07:52:50.914 !MESSAGE Import resulted in 1 errors !SUBENTRY 1 org.teiid.designer.jdbc.relational 4 0 2009-09-22 07:52:50.914 !MESSAGE Unexpected exception while creating relational model from BQT O11 !STACK 0 java.lang.NullPointerException at com.metamatrix.modeler.jdbc.relational.impl.custom.OracleModelProcessor.computeNameInSource(OracleModelProcessor.java:274) at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.setNameAndNameInSource(RelationalModelProcessorImpl.java:2441) at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.createParameters(RelationalModelProcessorImpl.java:2192) at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.createNewObject(RelationalModelProcessorImpl.java:1129) at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.performExecute(RelationalModelProcessorImpl.java:816) at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl$1.run(RelationalModelProcessorImpl.java:336) at com.metamatrix.modeler.internal.core.ModelEditorImpl.executeAsTransaction(ModelEditorImpl.java:541) at com.metamatrix.modeler.internal.core.ModelEditorImpl.executeAsTransaction(ModelEditorImpl.java:584) at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.executeWithinTransaction(RelationalModelProcessorImpl.java:343) at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.executeWithinTransaction(RelationalModelProcessorImpl.java:319) at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.execute(RelationalModelProcessorImpl.java:309) at com.metamatrix.modeler.internal.jdbc.ui.wizards.JdbcImportWizard.runFinish(JdbcImportWizard.java:677) at com.metamatrix.modeler.internal.jdbc.ui.wizards.JdbcImportWizard$1.run(JdbcImportWizard.java:262) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) !SUBENTRY 1 org.teiid.designer.compare 0 60002 2009-09-22 07:52:50.914 !MESSAGE Merging completed 2 - I tried a different approach where I imported tables and then imported (update) to get the procedures. I deselected all procedures and added these: SP_ALL_SMALLA_ROWS, SP_COUNTSMALLA, SP_COUNT_ALL_SMALLA_ROWS, SP_COUNT_ROWS_BETWEEN, and SP_ROWS_BETWEEN. The result was no tables and only the name of the SP_ALL_SMALLA_ROWS procedure (no actual procedure). The Review Updates panel of the wizard shows only one new entry: SP_ALL_SMALLA_ROWS. Clicking Finish produces the error. -- 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, 4 months

2
10
0 / 0

[JBoss JIRA] Created: (TEIIDDES-501) Remove the workaround created for TEIIDDES-500

by John Doyle (JIRA)

Remove the workaround created for TEIIDDES-500 ---------------------------------------------- Key: TEIIDDES-501 URL: https://jira.jboss.org/browse/TEIIDDES-501 Project: Teiid Designer Issue Type: Task Components: Eclipse Integration Affects Versions: 7.1 Reporter: John Doyle Assignee: John Doyle Fix For: 7.1 TEIIDDES-500 required a workaround for TEIID-1141. When the fix for 1141 is pulled into designer, the workaround should be removed. -- 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, 4 months

2
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues July 2010