February 2009 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-113) Ability to create partial copy of a model with new model wizard

by Barry LaFond (JIRA)

Ability to create partial copy of a model with new model wizard --------------------------------------------------------------- Key: TEIIDDES-113 URL: https://jira.jboss.org/jira/browse/TEIIDDES-113 Project: Teiid Designer Issue Type: Feature Request Components: Modeling Affects Versions: 6.0 Reporter: Barry LaFond Need to be able to create a new model from existing model (copy) and weed-out unwanted model children. Designer 5.5.3 version contained this feature, but after further review, the design was incomplete and has resulted in multiple bugs. So, plan is to remove this feature for the 6.0.0 release and then re-design & implement for 6.1.0 -- 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

12 years, 8 months

1
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-116) Add ability to perform partial copy model operations in new model wizard

by Barry LaFond (JIRA)

Add ability to perform partial copy model operations in new model wizard ------------------------------------------------------------------------ Key: TEIIDDES-116 URL: https://jira.jboss.org/jira/browse/TEIIDDES-116 Project: Teiid Designer Issue Type: Sub-task Components: Modeling Affects Versions: 6.0.0 Reporter: Barry LaFond Fix For: 6.1.0 -- 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

12 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-74) JDBC Importer "broke" after using it all morning - Unhandled event loop & Null arguments

by Paul Nittel (JIRA)

JDBC Importer "broke" after using it all morning - Unhandled event loop & Null arguments ---------------------------------------------------------------------------------------- Key: TEIIDDES-74 URL: https://jira.jboss.org/jira/browse/TEIIDDES-74 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 6.0 Environment: fedora 10 using the latest snapshot Reporter: Paul Nittel I played with the imported all morning (was having difficulties importing from derby. I had previously imported from Oracle and MySql.) I start the Designer I create a new project I right-click my project > Import Choose the jdbc metadata importer Click Next - nothing happens Click Next again - Goes to Select JDBC Source Configuration screen, but all controls are disabled except Back and Cancel. Even the combo box is dead. I found the following in the .metadata/.log file. !SESSION 2009-02-12 13:03:56.726 ----------------------------------------------- eclipse.buildId=M20080911-1700 java.version=1.6.0_10 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US Command-line arguments: -os linux -ws gtk -arch x86 !ENTRY com.metamatrix.modeler.dqp 1 0 2009-02-12 13:04:03.629 !MESSAGE starting workspace execution with url = "jdbc:metamatrix:admin@mmrofile:/home/pnittel/TeiidWorkspace1/.metadata/.plugins/com.metamatrix.modeler.dqp/vdb-execution/workspace.properties;version=1;XMLFormat=Tree;sqlOptions=SHOWPLAN;EmbeddedContext=Designer;dqp.logFile=/home/pnittel/TeiidWorkspace1/.metadata/.plugins/com.metamatrix.modeler.dqp/vdb-execution/workspace-13_04_03_Feb_12.log; !ENTRY org.eclipse.ui 4 0 2009-02-12 13:04:30.386 !MESSAGE Unhandled event loop exception !STACK 0 java.lang.IllegalArgumentException: Argument cannot be null at org.eclipse.swt.SWT.error(SWT.java:3761) at org.eclipse.swt.SWT.error(SWT.java:3695) at org.eclipse.swt.SWT.error(SWT.java:3666) at org.eclipse.swt.widgets.Widget.error(Widget.java:446) at org.eclipse.swt.widgets.Combo.add(Combo.java:163) at com.metamatrix.ui.internal.util.WidgetUtil.setComboItems(WidgetUtil.java:917) at com.metamatrix.ui.internal.util.WidgetUtil.setComboItems(WidgetUtil.java:895) at com.metamatrix.ui.internal.util.WidgetFactory.createCombo(WidgetFactory.java:441) at com.metamatrix.ui.internal.util.WidgetFactory.createCombo(WidgetFactory.java:411) at com.metamatrix.modeler.internal.jdbc.ui.wizards.JdbcSourceSelectionPage.createControl(JdbcSourceSelectionPage.java:184) at com.metamatrix.ui.internal.wizard.AbstractWizard.createPageControls(AbstractWizard.java:109) at com.metamatrix.ui.internal.wizard.AbstractWizard.createPageControls(AbstractWizard.java:97) at com.metamatrix.modeler.internal.jdbc.ui.wizards.JdbcImportWizard.createPageControls(JdbcImportWizard.java:219) at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:669) at org.eclipse.jface.wizard.WizardDialog.setWizard(WizardDialog.java:1083) at org.eclipse.jface.wizard.WizardDialog.updateForPage(WizardDialog.java:1142) at org.eclipse.jface.wizard.WizardDialog.access$2(WizardDialog.java:1139) at org.eclipse.jface.wizard.WizardDialog$4.run(WizardDialog.java:1128) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1126) at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:820) at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:369) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1158) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3401) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3033) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.ui.internal.handlers.WizardHandler$Import.executeHandler(WizardHandler.java:146) at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:273) at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:281) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476) at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169) at org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:247) at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:157) at org.eclipse.ui.internal.actions.CommandAction.run(CommandAction.java:171) at org.eclipse.ui.actions.ImportResourcesAction.run(ImportResourcesAction.java:97) at org.eclipse.ui.actions.BaseSelectionListenerAction.runWithEvent(BaseSelectionListenerAction.java:168) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:583) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:500) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1158) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3401) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3033) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2382) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2198) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:488) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:386) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504) at org.eclipse.equinox.launcher.Main.run(Main.java:1236) -- 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, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-75) Source Driver Installation Example (wiki) must include step to add necessary jar files

by Paul Nittel (JIRA)

Source Driver Installation Example (wiki) must include step to add necessary jar files -------------------------------------------------------------------------------------- Key: TEIIDDES-75 URL: https://jira.jboss.org/jira/browse/TEIIDDES-75 Project: Teiid Designer Issue Type: Bug Affects Versions: 6.0 Environment: fedora 10 Reporter: Paul Nittel The first time a connector is added for previewing, the jar must be added through the UDF jar mechanism. Once that's done, the jar is added to the plugins dql extensions directory and it remains there, even if the jar is removed from the UDF view. Need to add this step to the example in the wiki. -- 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, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-115) Remove ability to perform partial copy model operations in new model wizard.

by Barry LaFond (JIRA)

Remove ability to perform partial copy model operations in new model wizard. ---------------------------------------------------------------------------- Key: TEIIDDES-115 URL: https://jira.jboss.org/jira/browse/TEIIDDES-115 Project: Teiid Designer Issue Type: Sub-task Components: Modeling Affects Versions: 6.0.0 Reporter: Barry LaFond Fix For: 6.0.0 Because the design is flawed, this sub-feature continues to generate defects. The purpose of this task is to remove this sub-feature. -- 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, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-112) Function Model Diagram Object Positions Can't Be Persisted

by Dan Florian (JIRA)

Function Model Diagram Object Positions Can't Be Persisted ---------------------------------------------------------- Key: TEIIDDES-112 URL: https://jira.jboss.org/jira/browse/TEIIDDES-112 Project: Teiid Designer Issue Type: Bug Components: Diagrams Affects Versions: 6.0 Reporter: Dan Florian With the FunctionDefinitions.xmi Model Editor open, import a UDF zip file. After the import, move some of the diagram objects around and Save. Notice that the diagram obects positions change back to their original positions. It is impossible to persist changes in diagram object positions. Barry L. mentioned that this sounds like a problem in diagram object caching. -- 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, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-117) JDBC driver JARs added when creating a new JDBC source at import time should be added as extension JARs so the connector works at runtime.

by Ken Johnson (JIRA)

JDBC driver JARs added when creating a new JDBC source at import time should be added as extension JARs so the connector works at runtime. ------------------------------------------------------------------------------------------------------------------------------------------ Key: TEIIDDES-117 URL: https://jira.jboss.org/jira/browse/TEIIDDES-117 Project: Teiid Designer Issue Type: Feature Request Components: Import/Export Affects Versions: 6.0.0 Environment: Ganymede 3.4.1 JEE environment + Teiid Designer 6.0.0 pre-release. Reporter: Ken Johnson Given that Designer does not bundle any JDBC driver JARs, the need to be added by the user. Currently they are required in two places: 1. when defining an import source 2. for the connector used during preview and testing (extension jar) The user has to deal with importing the driver JARs in two different ways to support the logical operation of Import->Model->Preview. Suggest: a) providing a single new mechanism for adding driver JARs to the tooling so they are available for both Import and Preview/Execution, or b) automatically add extension JAR for Preview/Execution when specifying driver JAR during import source configuration, or c) both In the present implementation, a novice user will have a heck of a time understanding why Preview doesn't work when they just added the JAR while configuring the source for import. -- 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, 11 months

3
7
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-88) Creating base table in view model doesn't use auto-naming feature

by Barry LaFond (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-88?page=com.atlassian.jira.pl... ] Barry LaFond updated TEIIDDES-88: --------------------------------- Component/s: Views Fix Version/s: 6.1.0 (was: 6.0.0) Affects Version/s: 6.0.0 Assignee: (was: Barry LaFond) > Creating base table in view model doesn't use auto-naming feature > ----------------------------------------------------------------- > > Key: TEIIDDES-88 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-88 > Project: Teiid Designer > Issue Type: Task > Components: Views > Affects Versions: 6.0.0 > Environment: Linux > Reporter: Paul Nittel > Fix For: 6.1.0 > > > When adding a base table to a relational view model, it names it NewBaseTable and requires the user to manually rename the table. It should be coming up in rename mode. -- 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

15 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-90) No auto rename when adding elements to XML document

by Barry LaFond (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-90?page=com.atlassian.jira.pl... ] Barry LaFond updated TEIIDDES-90: --------------------------------- Component/s: Views Fix Version/s: 6.1.0 (was: 6.0.0) Affects Version/s: 6.0.0 Assignee: (was: Barry LaFond) > No auto rename when adding elements to XML document > --------------------------------------------------- > > Key: TEIIDDES-90 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-90 > Project: Teiid Designer > Issue Type: Task > Components: Views > Affects Versions: 6.0.0 > Environment: Linux > Reporter: Paul Nittel > Fix For: 6.1.0 > > > I'm following the E2E XML Schemaless BookListing test script which calls for manually adding a number of elements to a document model. As I add each one, the name "NewXmlElement" is displayed. To change that name, I have to right-click > Rename. > Should be auto-renaming for me. (And the model is open in the editor.) -- 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

15 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-92) Designer: Export / Import of a ModelProject set should carry along the connector binding info.

by Barry LaFond (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-92?page=com.atlassian.jira.pl... ] Barry LaFond updated TEIIDDES-92: --------------------------------- Component/s: Data Preview Fix Version/s: 6.1.0 (was: 6.0.0) Affects Version/s: 6.0.0 Assignee: (was: Barry LaFond) > Designer: Export / Import of a ModelProject set should carry along the connector binding info. > ---------------------------------------------------------------------------------------------- > > Key: TEIIDDES-92 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-92 > Project: Teiid Designer > Issue Type: Feature Request > Components: Data Preview > Affects Versions: 6.0.0 > Reporter: Mark Drilling > Priority: Minor > Fix For: 6.1.0 > > > This is a request resulting from the preview Query development work. Export of a ModelProject set should carry along the connector binding info, so that when it is reImported the bindings are also imported. -- 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

15 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues February 2009