[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
[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
[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
[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