December 2009 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-244) Text Connector does not show up after creation

by Mark Drilling (JIRA)

Text Connector does not show up after creation ---------------------------------------------- Key: TEIIDDES-244 URL: https://jira.jboss.org/jira/browse/TEIIDDES-244 Project: Teiid Designer Issue Type: Bug Components: VDB & Execution Affects Versions: 6.2.0 Reporter: Mark Drilling Assignee: Barry LaFond In 6.2 Teiid Designer, create a new Text Connector in ConnectorsView. The Connector does not display anywhere. If I try to create another text connector with the same name, the wizard says a connector with that name already exists. In the VDB editor, the Text Connector does not show up as one of the available connectors. -- 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, 3 months

2
1
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, 3 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, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-144) Problem Importing XSD via the "XSD as Relational Source Model" importer

by Mark Drilling (JIRA)

Problem Importing XSD via the "XSD as Relational Source Model" importer ----------------------------------------------------------------------- Key: TEIIDDES-144 URL: https://jira.jboss.org/jira/browse/TEIIDDES-144 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 6.0.0, 6.1.0, Future Reporter: Mark Drilling Assignee: Mark Drilling Priority: Minor Fix For: 6.0.0 Customer Issue Tracker number 282405. Import of the customer xsd throws NPEs and fails to complete. -- 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, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-145) DqpUiPlugin References Wrong Class When Constructing i18n Prefix

by Dan Florian (JIRA)

DqpUiPlugin References Wrong Class When Constructing i18n Prefix ---------------------------------------------------------------- Key: TEIIDDES-145 URL: https://jira.jboss.org/jira/browse/TEIIDDES-145 Project: Teiid Designer Issue Type: Bug Components: Dialogs Affects Versions: 6.0.0 Reporter: Dan Florian Assignee: Dan Florian Fix For: 6.0.0 The title of the dialog shown by DqpUiPlugin.showErrorDialog had a missing i18n key. Tracked this down to an error in the PREFIX constant. -- 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, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-147) Provide Connector types for native drivers

by Ramesh Reddy (JIRA)

Provide Connector types for native drivers ------------------------------------------ Key: TEIIDDES-147 URL: https://jira.jboss.org/jira/browse/TEIIDDES-147 Project: Teiid Designer Issue Type: Task Components: Teiid Integration Affects Versions: 6.0.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 6.0.0 Currently we are only supplying the Data Direct specific connector types in the "configuration.xml". Based on the user requests in forums, this is major point of confusion as all the users were looking for connector types based on the native drivers provided by vendors like Oracle or MS. Based on the conversation with team leads we should support the native types and remove the Data Direct types, and provide data direct as needed as separate file. -- 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, 3 months

3
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-151) Importing a previously exported connector fails to start after import

by Paul Nittel (JIRA)

Importing a previously exported connector fails to start after import --------------------------------------------------------------------- Key: TEIIDDES-151 URL: https://jira.jboss.org/jira/browse/TEIIDDES-151 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 6.0.0 Environment: Fedora 10, Barry's 4/7/09 and Dan's 4/16/09 builds Reporter: Paul Nittel Using Barry's build, I exported the connector for Products XA Oracle 9i. Switching to Dan's build, I imported the CDK and jar (which was ignored since it was already in my configuration). When I tried to preview data using this connector, it failed to start. Stuff attached: Project, .CDK, .JAR TEIIDDES-150 is related. -- 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, 3 months

3
8
0 / 0

[JBoss JIRA] Created: (TEIIDDES-146) ClassCastException (String to EObject) when adding attributes to transformation using reconciler

by Paul Nittel (JIRA)

ClassCastException (String to EObject) when adding attributes to transformation using reconciler ------------------------------------------------------------------------------------------------ Key: TEIIDDES-146 URL: https://jira.jboss.org/jira/browse/TEIIDDES-146 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 6.0.0 Environment: fedora 10, 4/7/09 build Reporter: Paul Nittel Attachments: ExportedLog.log I followed the Procedural-Relational Mapping test script, but didn't quite get the results I expected, so I modified the transformation by removing two attributes (EmployeeFullNameID and EmployeeAddressID). After realizing that was a dumb move, I set about to add them back into the transformation. I started the reconciler, clicked the Add button, and added both EmployeeID and EmployeeID1 as new attributes. I then renamed them to EmployeeFullNameID and EmployeeAddressID. I clicked OK to close the Reconciler. The transformation did not have the new attributes and the model wasn't marked "dirty". I found exceptions in the Message Log like this one: Error 2009-04-15 08:23:57.961 Unhandled event loop exception java.lang.ClassCastException: java.lang.String cannot be cast to org.eclipse.emf.ecore.EObject at com.metamatrix.modeler.transformation.ui.reconciler.Binding.applyAttrNameModification(Binding.java:314) at com.metamatrix.modeler.transformation.ui.reconciler.ReconcilerObject.applyTargetAttributeRenames(ReconcilerObject.java:683) at com.metamatrix.modeler.transformation.ui.reconciler.QueryReconcilerHelper.applyPreModifications(QueryReconcilerHelper.java:189) at com.metamatrix.modeler.transformation.ui.reconciler.ReconcilerPanel.applyPreModifications(ReconcilerPanel.java:555) at com.metamatrix.modeler.transformation.ui.reconciler.ReconcilerDialog.applyPreModifications(ReconcilerDialog.java:110) at com.metamatrix.modeler.transformation.ui.actions.ReconcileTransformationAction$1.run(ReconcileTransformationAction.java:253) at com.metamatrix.ui.internal.viewsupport.UiBusyIndicator.showWhile(UiBusyIndicator.java:80) at com.metamatrix.modeler.transformation.ui.actions.ReconcileTransformationAction.doRun(ReconcileTransformationAction.java:247) at com.metamatrix.ui.actions.AbstractAction$1.run(AbstractAction.java:554) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at com.metamatrix.ui.actions.AbstractAction.run(AbstractAction.java:557) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) 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$6.handleEvent(ActionContributionItem.java:452) 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) The whole log is attached. -- 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, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-148) Designer produces error telling user to look at log file and log file has the same error telling user to look at log file - no details on what the error is

by Warren Gibson (JIRA)

Designer produces error telling user to look at log file and log file has the same error telling user to look at log file - no details on what the error is ----------------------------------------------------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-148 URL: https://jira.jboss.org/jira/browse/TEIIDDES-148 Project: Teiid Designer Issue Type: Bug Affects Versions: 6.0.0 Environment: Windows client Reporter: Warren Gibson Priority: Minor There may be more that one defect here but I am not sure. Designer produces error telling user to look at the log file AND when user looks at log file it also tells the user to look at the log file:-). No details on what the error is. I imported a connector which had been exported from a 5.5.3 console. During the import the wizard asked me to find 2 jars files which it need (MJjdbc and jdbcconn . After finding the jars the import completed. However, I noticed the above error in the message log. The log also contains two other error situations which I don't believe have anything to do with this one but I could be wrong. Please take a look at the other two exceptions and let me know if they should be logged as a defect. Log attached. -- 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, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-149) Creating new connector binding - started to put user name on binding and got two dialogs with "null" and nothing else

by Warren Gibson (JIRA)

Creating new connector binding - started to put user name on binding and got two dialogs with "null" and nothing else --------------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-149 URL: https://jira.jboss.org/jira/browse/TEIIDDES-149 Project: Teiid Designer Issue Type: Bug Environment: Windows Reporter: Warren Gibson Started to create a new Oracle connector binding for BooksA and when I started to enter the user two dialogs appeared with nothing on them except "null". See attachment. -- 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, 3 months

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues December 2009