June 2009 - teiid-designer-issues

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

2
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-161) Importing Connector (.cdk) with over existing connector deletes driver jar

by Barry LaFond (JIRA)

Importing Connector (.cdk) with over existing connector deletes driver jar -------------------------------------------------------------------------- Key: TEIIDDES-161 URL: https://jira.jboss.org/jira/browse/TEIIDDES-161 Project: Teiid Designer Issue Type: Bug Components: VDB & Execution Affects Versions: 6.0.0 Reporter: Barry LaFond Assignee: Barry LaFond Priority: Critical Fix For: 6.0.0 In new workspace.... 1) Import Model from JDBC (connector is created and bound to source) 2) Preview table and see data 3) Select new connector in Connectors View and "Export Connector" to file system 4) Import that same connector back into Designer 5) Results in deleted jar 6) Preview fails This is because when replacing a connector (overwriting) we first "Delete" the connector and auto-delete unused connector jars. In this case the "Importer" indicated the jar already existed and would not be imported. But it was too late, the next step in the process deleted the jar that was supposed to remain. Fix is to change our philosophy and NOT auto-delete jars when they are NOT used. -- 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-154) Attempting to use JDBC metadata importer gets Argument cannot be null

by Paul Nittel (JIRA)

Attempting to use JDBC metadata importer gets Argument cannot be null --------------------------------------------------------------------- Key: TEIIDDES-154 URL: https://jira.jboss.org/jira/browse/TEIIDDES-154 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 6.0.0 Environment: fedora 10, Teiid Designer 090421 Reporter: Paul Nittel Attachments: BustedImported.jpg After successfullky importing from a few sources, I went back to try one more. This time, however, I couldn't get the JDBC Importer to work. Here's the sad tale: Choose File > Import Select the JDBC metadata importer Click Next <wait a long time> Get next screen, but sources combo box and Next button are disabled. Somewhere along the way I get an exception like: Error 2009-04-21 14:59:08.708 Unhandled event loop exception 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.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) Whole log and screenshot are 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, 11 months

2
7
0 / 0

[JBoss JIRA] Created: (TEIIDDES-153) WSDL to Relational Importer needs to set Name in source for input columns.

by John Doyle (JIRA)

WSDL to Relational Importer needs to set Name in source for input columns. -------------------------------------------------------------------------- Key: TEIIDDES-153 URL: https://jira.jboss.org/jira/browse/TEIIDDES-153 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 6.0.0 Reporter: John Doyle Assignee: John Doyle Name in source now seems required for all columns, and the WSDL to Relational Importer has never that this on input columns. -- 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
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-162) Connectors are still referred to Connector Bindings in many labels and titles

by Barry LaFond (JIRA)

Connectors are still referred to Connector Bindings in many labels and titles ----------------------------------------------------------------------------- Key: TEIIDDES-162 URL: https://jira.jboss.org/jira/browse/TEIIDDES-162 Project: Teiid Designer Issue Type: Bug Components: Dialogs Affects Versions: 6.0.0 Reporter: Barry LaFond Assignee: Barry LaFond Fix For: 6.0.0 We're still calling Connectors by Connector Bindings. Need to replace all verbage with "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, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-156) Error post processing import (extension class=class com.metamatrix.modeler.internal.dqp.ui.jdbc.ConnectorBindingImportPostProcessor)

by Warren Gibson (JIRA)

Error post processing import (extension class=class com.metamatrix.modeler.internal.dqp.ui.jdbc.ConnectorBindingImportPostProcessor) ------------------------------------------------------------------------------------------------------------------------------------ Key: TEIIDDES-156 URL: https://jira.jboss.org/jira/browse/TEIIDDES-156 Project: Teiid Designer Issue Type: Bug Environment: Teiid Designer on Windows importing Oracle Reporter: Warren Gibson Imported Books Oracle and received a Stack Trace: java.net.MalformedURLException: unknown protocol: d at java.net.URL.<init>(Unknown Source) at java.net.URL.<init>(Unknown Source) at java.net.URL.<init>(Unknown Source) at com.metamatrix.modeler.internal.dqp.ui.jdbc.ConnectorBindingImportPostProcessor.postProcess(ConnectorBindingImportPostProcessor.java:157) at com.metamatrix.modeler.internal.jdbc.ui.wizards.JdbcImportWizard.runFinish(JdbcImportWizard.java:691) 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) The imported tables appeared in the Modeler Explorer but I am unable to preview them. -- 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues June 2009