September 2009 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-194) jdbc Oracle import does not create connector

by Luca Gioppo (JIRA)

jdbc Oracle import does not create connector -------------------------------------------- Key: TEIIDDES-194 URL: https://jira.jboss.org/jira/browse/TEIIDDES-194 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 6.0.0 Environment: eclipse.buildId=M20080911-1700 java.version=1.6.0_04 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=it_IT Command-line arguments: -os win32 -ws win32 -arch x86 Reporter: Luca Gioppo Importing model from jdbc Creating a new source for an Oracle 9 DB using jdbc14.jar and adding to udf (and a second time in the source definition) the jar from the oracle instant client the connection work, tables are imported but at hte end of the import the error is: Error post processing import (extension class=class com.metamatrix.modeler.internal.dqp.ui.jdbc.ConnectorBindingImportPostProcessor) -- 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

13 years, 9 months

2
6
0 / 0

[JBoss JIRA] Created: (TEIIDDES-121) Simplify Adding Connector Jar as UDF jar in UDF view

by Barry LaFond (JIRA)

Simplify Adding Connector Jar as UDF jar in UDF view ---------------------------------------------------- Key: TEIIDDES-121 URL: https://jira.jboss.org/jira/browse/TEIIDDES-121 Project: Teiid Designer Issue Type: Feature Request Components: Views Affects Versions: 6.1.0 Reporter: Barry LaFond Priority: Minor Fix For: 6.1.0 Current UDF view provides two actions: Import UDF Extension Jars & Add Connector Jars to UDF The second action is somewhat redundant. Request moving the functionality of the second action into an "Advanced" section of the dialog from the first action. -- 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

13 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (TEIIDDES-174) Closing Project does not hide project-specific source bindings in Connectors View

by Barry LaFond (JIRA)

Closing Project does not hide project-specific source bindings in Connectors View --------------------------------------------------------------------------------- Key: TEIIDDES-174 URL: https://jira.jboss.org/jira/browse/TEIIDDES-174 Project: Teiid Designer Issue Type: Bug Components: Views Affects Versions: 6.0.0 Reporter: Barry LaFond Priority: Minor Fix For: Future 1) Import Books or Parts and verify Connectors and Source Binding is created in Connectors View 2) Right-click Project and "Close Project" 3) Source bindings still visible (should be removed) 4) Select/deselect the "Hide Connectors Types" button on Connectors view toolbar 5) Sources bindings are now hidden. 6) Re-open project and Source bindings now visible Problem with refresh on Connectors View during Project Close action. -- 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

13 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (TEIIDDES-190) There is no way to hand model a XML-Relational source.

by John Doyle (JIRA)

There is no way to hand model a XML-Relational source. ------------------------------------------------------ Key: TEIIDDES-190 URL: https://jira.jboss.org/jira/browse/TEIIDDES-190 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 6.0.0 Reporter: John Doyle Fix For: 6.1.1 We used to ship the model extensions for XML-R modeling with the importer, and now we generate them on demand with the importer. However, if a user needs to hand model from scratch, perhaps because there is no XSD, there is no model extension to depend on. We need to provide a way to create just the extension. -- 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

13 years, 10 months

1
5
0 / 0

[JBoss JIRA] Created: (TEIIDDES-129) WSDL to Relational Importer models only one service from a WSDL defining multiple services.

by John Doyle (JIRA)

WSDL to Relational Importer models only one service from a WSDL defining multiple services. ------------------------------------------------------------------------------------------- Key: TEIIDDES-129 URL: https://jira.jboss.org/jira/browse/TEIIDDES-129 Project: Teiid Designer Issue Type: Bug Components: Import/Export Reporter: John Doyle Assignee: John Doyle Attachments: pricelist_twoServices.wsdl The attached WSDL defined two services. When importing from this WSDL, the importer UI correctly displays the metadata of the two services, but only the model for one is generated by the importer. We need to generate multiple models and bindings for this case. -- 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

13 years, 10 months

2
7
0 / 0

[JBoss JIRA] Created: (TEIIDDES-208) Salesforce Importer throws javax.net.ssl.SSLException when validating credentials.

by John Doyle (JIRA)

Salesforce Importer throws javax.net.ssl.SSLException when validating credentials. ---------------------------------------------------------------------------------- Key: TEIIDDES-208 URL: https://jira.jboss.org/jira/browse/TEIIDDES-208 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 6.1.0 Reporter: John Doyle Assignee: John Doyle Fix For: Future Salesforce Importer throws javax.net.ssl.SSLException when validating credentials. The full text of the message is: javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLException: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty This occurs because the cacerts file is not found. -- 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

13 years, 10 months

1
6
0 / 0

[JBoss JIRA] Created: (TEIIDDES-176) Desinger needs to embed "Teiid Embedded" as a plugin, with only dependencies to "public" APIs.

by Ramesh Reddy (JIRA)

Desinger needs to embed "Teiid Embedded" as a plugin, with only dependencies to "public" APIs. ---------------------------------------------------------------------------------------------- Key: TEIIDDES-176 URL: https://jira.jboss.org/jira/browse/TEIIDDES-176 Project: Teiid Designer Issue Type: Feature Request Components: Teiid Integration Reporter: Ramesh Reddy Assignee: Johnny Verhaeg Priority: Critical > On Wed, 2009-05-06 at 11:35 -0400, John Doyle wrote: >> I'm throwing this idea out there with very little idea of how the >> links between Teiid and Designer function, but I think it would be >> cool and beneficial. >> >> AFAIK we don't have a user story abut how you update the version of >> Teiid that is delivered with Designer. I think that it would be >> very cool if we exposed this cabability in designer similar to the >> way Installed JREs are exposed through the Preferences page. >> Designer could come with a version of Teiid, but users could point >> Designer to other versions of Teiid installed on their system and >> choose to run with those. One of the goals we have discussed is >> that we don't want Designer to be wedded to a particular version of >> Teiid. Defining the links between to two in this manner would >> force a contract and make it easy to test and validate that >> Designer 6.X works with Teiid 6.X and 7.X, etc. >> >> What do you think? > Well that is certainly the case going forward to have such modularity, > as this has been discussed before. However, that is not case today. > There needs to be huge re-work needs to be done in designer before we > can achieve this. Currently Designer knows too much about the Teiid's > configuration, that needs to be fixed such that it only communicates > only through the known public API like JDBC and Admin API. > > Ramesh.. -- 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

13 years, 10 months

3
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-168) Designer fails to delete project.

by John Doyle (JIRA)

Designer fails to delete project. --------------------------------- Key: TEIIDDES-168 URL: https://jira.jboss.org/jira/browse/TEIIDDES-168 Project: Teiid Designer Issue Type: Bug Affects Versions: 6.0.0 Environment: Designer 4-27 snapshot build on Fedora 10. Reporter: John Doyle I have two projects that models of the same name. When I try to delete the project in the Model Explorer, I am prompted that I am trying to delete a model when a model in another project depends upon it. As far as I can tell this is not true, and I'm surmising it's getting confused by the name. In any event, when I tell the designer to delete anyway, the delete does not happen. -- 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

13 years, 11 months

2
5
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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues September 2009